Wordpress LScache Plugin: LS Cache not being purged when widgets are saved/added
Last Updated on: Wed, 15 Apr 2026 00:00:02 Ive been using LiteSpeed on my servers and my sites for several years. Whenever I updated a widget (or added a widget) on one of my sites in the past, the LiteSpeed cache would automatically be purged, and my site would show the content from my edits. With the most recent updates to LiteSpeed, though, the LiteSpeed cache isnt being purged when I save a widget or add a new widget. I now have to purge the LiteSpeed cache manually after every edit I make in the widget interface. Im experiencing this problem with default WordPress themes and with all plugins (other than LiteSpeed) deactivated. Hello, Is ESI option set up? You can use Litespeed cache -> Report -> Send to Litespeed option and post the report number here. Hi Tishu, Thanks for the reply. I hadnt seen the ESI setting before ? Ive set that up and Im now seeing my widgets update after I make a change in them and then save them. So if I set the ESI setting in a widget to Disable , that turns off all caching for that widget, correct? Jason Hi, Jason. It actually disables ESI for that particular widget altogether. If you want to keep ESI enabled, but keep the widget uncached, you can set it to Public or Private (it doesnt matter which one) and set the TTL to 0. Theres a blog post about how ESI works here, if youd like to know more. Hope this helps! P.S. To clarify: when I say it disables ESI for that particular widget, what I mean is that the widget is no longer considered to be an ESI block. It is treated as part of the full page. In order for a widget to be handled separately from the page it is on, it needs to be considered an ESI block. Reason: Added clarification
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference