We should maybe add in something that moves open WHMCS tabs to our homepage after some time, or would that be too annoying? Actually I'm not sure if it's even possible to do efficiently. I need to remember again how the ban logic works very specifically to see what page(s) need to be targeted.
Not sure how you have implemented the captcha/ban logic, but I guess it would make sense that when the session expires, it automatically redirects a user to another page (which is not behind any captcha or ban logic) and it just states something along the lines that their session has expired with a link to take them back to the login page.
I'm about to majorly mess with the backend notifications. This will (1) break backend notifications hardcore, (2) mess it up to where if you don't reload the frontend (vps.blackfriday) after the updates it won't send you any or I don't know, (3) could probably cause a lot of other problems related to not having the page open and expecting to receive alerts, and/or even accidentally bring up these notifications when they shouldn't appear on the frontend.
I'll let you guys know when it's all done so you can do a reload and then report any bugs. Until then any weirdness with it is expected.
The deal page is a bit of a disaster, with CPU rev up high if I keep the page open.
Feels like the page in mining bitcoins, I think we could do with a bit less graphics.
@ZA_capetown said:
There were some flashes and some extra long 'loading offer' (Checking for offer...), but nothing seemed to have exploded, yet
Due to the way caching works after a restart it takes a bit for it to re-establish the connection and without a connection it's set to keep reloading until it finds one.
@evnix said:
The deal page is a bit of a disaster, with CPU rev up high if I keep the page open.
Feels like the page in mining bitcoins, I think we could do with a bit less graphics.
It's these things that do most the damage.
Added a toggle box to disable it, might not be available on all devices/views and it might cause other unintended bugs. I'll fix it later maybe. But I think it works okay right now, maybe. Might need a reload.
Edit -- Actually I might be wrong about that, seems like it's definitely a little of everything. We even have two sets of constant animations on the entire background. I'll slowly add in other stuff to this toggle.
Updates to backend notifications have been pushed out. Reload your frontend. It should now try to respect your notification settings for backend notifications too. I don't know if it works or not, it does appear to be working in terms of logs though, I just don't know if it's actually sending anything as I've had the frontend open. Let me know.
Picked up a small storage- that concludes (hopefully) by BF 2024 with Virmach... the VPS offers are great but not my cup of tea, location/ spec wise. Best wishes to the remaining time/ sales....
@ZA_capetown said:
There were some flashes and some extra long 'loading offer' (Checking for offer...), but nothing seemed to have exploded, yet
Due to the way caching works after a restart it takes a bit for it to re-establish the connection and without a connection it's set to keep reloading until it finds one.
@evnix said:
The deal page is a bit of a disaster, with CPU rev up high if I keep the page open.
Feels like the page in mining bitcoins, I think we could do with a bit less graphics.
It's these things that do most the damage.
Added a toggle box to disable it, might not be available on all devices/views and it might cause other unintended bugs. I'll fix it later maybe. But I think it works okay right now, maybe. Might need a reload.
Edit -- Actually I might be wrong about that, seems like it's definitely a little of everything. We even have two sets of constant animations on the entire background. I'll slowly add in other stuff to this toggle.
Updates to backend notifications have been pushed out. Reload your frontend. It should now try to respect your notification settings for backend notifications too. I don't know if it works or not, it does appear to be working in terms of logs though, I just don't know if it's actually sending anything as I've had the frontend open. Let me know.
It seems to have muted all notifications. Front and back!!
Sigh now I need to rely on other sources foe notifications 😒 😪 🙄 😕 😑
@localhost said: It seems to have muted all notifications. Front and back!!
Sigh now I need to rely on other sources foe notifications 😒 😪 🙄 😕 😑
I've definitely been getting frontend notifications after the update, and no backend ones (as expected, I was previously affected by a bug that displayed backend on the frontend but didn't have anyone else confirming that.)
Testing to see if backend ones send now (for me.)
I'm seeing a lot of logs that indicate people haven't reloaded the frontend though, but more of them that show it successfully updated to a new subscription. Also seeing logs that show notification settings. Looking back at the logs I do actually see notifications being sent out as well.
Edit -- Okay it sent but not received, looking into it. Sent just means considered for sending, it might be the new filters (maybe something like percentage off being miscalculated.)
Comments
Not sure how you have implemented the captcha/ban logic, but I guess it would make sense that when the session expires, it automatically redirects a user to another page (which is not behind any captcha or ban logic) and it just states something along the lines that their session has expired with a link to take them back to the login page.
I'm about to majorly mess with the backend notifications. This will (1) break backend notifications hardcore, (2) mess it up to where if you don't reload the frontend (vps.blackfriday) after the updates it won't send you any or I don't know, (3) could probably cause a lot of other problems related to not having the page open and expecting to receive alerts, and/or even accidentally bring up these notifications when they shouldn't appear on the frontend.
I'll let you guys know when it's all done so you can do a reload and then report any bugs. Until then any weirdness with it is expected.
There were some flashes and some extra long 'loading offer' (Checking for offer...), but nothing seemed to have exploded, yet
The deal page is a bit of a disaster, with CPU rev up high if I keep the page open.
Feels like the page in mining bitcoins, I think we could do with a bit less graphics.
My Personal Blog | Currently Building LoadMyCode
Now you know how VirMach can sell servers so cheap :-)
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Unable to duplicate.. or find the unicorn plan I did yesterday
its the CPU
My Personal Blog | Currently Building LoadMyCode
Due to the way caching works after a restart it takes a bit for it to re-establish the connection and without a connection it's set to keep reloading until it finds one.
It's these things that do most the damage.
Added a toggle box to disable it, might not be available on all devices/views and it might cause other unintended bugs. I'll fix it later maybe. But I think it works okay right now, maybe. Might need a reload.
Edit -- Actually I might be wrong about that, seems like it's definitely a little of everything. We even have two sets of constant animations on the entire background. I'll slowly add in other stuff to this toggle.
Updates to backend notifications have been pushed out. Reload your frontend. It should now try to respect your notification settings for backend notifications too. I don't know if it works or not, it does appear to be working in terms of logs though, I just don't know if it's actually sending anything as I've had the frontend open. Let me know.
@VirMach - I'll pay $15 to transfer it... Give me anything on the East Coast... LMK, thanks
Picked up a small storage- that concludes (hopefully) by BF 2024 with Virmach... the VPS offers are great but not my cup of tea, location/ spec wise. Best wishes to the remaining time/ sales....
———-
blog | exploring visually |
It seems to have muted all notifications. Front and back!!
Sigh now I need to rely on other sources foe notifications 😒 😪 🙄 😕 😑
I've definitely been getting frontend notifications after the update, and no backend ones (as expected, I was previously affected by a bug that displayed backend on the frontend but didn't have anyone else confirming that.)
Testing to see if backend ones send now (for me.)
I'm seeing a lot of logs that indicate people haven't reloaded the frontend though, but more of them that show it successfully updated to a new subscription. Also seeing logs that show notification settings. Looking back at the logs I do actually see notifications being sent out as well.
Edit -- Okay it sent but not received, looking into it. Sent just means considered for sending, it might be the new filters (maybe something like percentage off being miscalculated.)
web notifications no
telegram notifications yes
compatible browsers are a never ending task