If you clear that directory then yes, any WordPress sites for that user would also have their cache files removed resulting in a cache miss the next time someone visits the site and hits the backend server.
If you are using a CDN like QUIC.cloud with WordPress, this would not affect any pages...
Hello @El Porcharo ,
In most cases the owner of the site should have an lscache directory that you can empty in /home/$user/lscache. Just be aware that this will also clear the cache for any other sites this user caches with LiteSpeed/lscache plugins.
Regards,
-Michael
Hello everyone,
It looks like my CSRF work is going to have remain paused for a few more days while I continue to work through a new mountain of time sensitive work that always seems to appear whenever I am in the middle of any tricky XF plugin changes 😅.
My intention is to get back to this...
Not yet but I've been able to put a good amount of work into a solution since the start of the new year. Hopeful to be able to achieve something useful through ESI in the near future.
Regards,
-Michael
Not yet but I've been able to put a good amount of work into a solution since the start of the new year. Hopeful to be able to achieve something useful through ESI in the near future.
Regards,
-Michael
Hello @Aivaras ,
I would recommend against this solution as it would likely be the same as disabling guest caching with how prevalent CSRF tokens are in XenForo.
On the same note, I'm looking into the plugin code now to see if it is possible to resolve this by having the plugin replace a...
I'd say that this forum is the best place for support with this plugin, but for something like that perhaps https://www.litespeedtech.com/support/forum/ would be better.
Edit: We also have a slack community which may make sense as well https://www.litespeedtech.com/slack
I'd say that this is close enough to the truth :)
@Mr Lucky If you can reproduce the encountered issues feel free to send me a DM with the details and I can try to look into things sometime next week.
Regards,
-Michael
Hello @daimpa ,
In this case, this is an expected behavior of a basic page cache. When the page is cached for a guest visitor, all information on that page including the number of online users displayed at that time are stored as a cache file and served "as is" until the cached page expires (in...
Hello @Kleazy,
@JustinHawk is correct here, your other addon is implementing this incorrectly.
For reference, this is the function definition we are extending here:
public function completeLogin(\XF\Entity\User $user, $remember)
The plugin itself is pretty simple so setting up the required rewrite rules is all the setup that needs to be done in most cases.
In case you missed it on the Overview page, here is the link to the installation guide:
https://docs.litespeedtech.com/lscache/lscxf/
Regards,
-Michael
[Improvement] Added "lost password confirm" as a do-not-cache page.
[Improvement] Misc code improvements.
[Bug Fix] Logged-in cookie is now cleared when a visitor is logged-out due to a session timeout.
[Bug Fix] Visitors automatically logged-in from the "forgot my password" submission page are...
Michael A. updated LiteSpeed Cache for XF2 - Community with a new update entry:
LiteSpeed Cache Plugin for XF2 v2.3.0
Read the rest of this update entry...