Wordpress LScache Plugin: Privately cache not working?
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello, Since last version we are seeing issues with ESI and Private cache. ESI shortcodes doesnt output for logged out users, to fix it, weve removed the ESI portion of the shortcode, which is conditional (it display the user name). Now, it seems that the private cache is also broken, as users are seeing cache versions of other users (with that, seeing the name of other users). Isnt the private cache supposed to be unique for each user? Hi, Did you enable ESI ? when you have ESI , there will be a certain public cache among all login users , and certain section of the page , to be private cache Best regards, Hi @CacheCrawler , It was working prior to the recent update. Here is the setting which was working: ? Private cache for login users ON ? ESI ON ? Using [esi shortcode] ? which display the user name on the front page or a login box. Important, this was working prior to the update. Now, after the update, most of times the shortcode result would be empty, at source code I could see the LiteSpeed ESI shortcode comments, but with nothing inside it. With user logged in, the shortcode was working as expected, showing his name. But, since the login form was missing, we had to deactivate the ESI and remove the [esi shortcode], leaving just the [shortcode] and keeping the Private cache for login On. After that, the login form from the shortcode started appearing again, but after login, some users were seeing the name of other users, meaning that they were seeing the cache version of other logged in users. It was a completely mess, so we had to deactivate the Cache functionality of the site until we find a fix. did you also enable object cache ? if so , please try it OFF I dont recall if there is any ESI change in recent updates but please try rollback to v4.x , see if it still works fine there , you can get it in https://wordpress.org/plugins/litespeed-cache/advanced/ , bottom of page Hi @CacheCrawler , We have re-activated without the Object Cache, and it seems to have fixed it. Well keep testing for the next hours. Ill let you know if anything strange happens. Thanks Hi @CacheCrawler , The error started happening again. Ill test at other time an older version.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference