Hi,
I have been using Litespeed Cache for a couple of months and the results are positive for the speed of websites, but not for cache management. The Joomla plugin does not work as it should and the behavior is not that described in the documentation https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscjoomla
This is not true: the entire cache is purged inappropriately following a series of events such as:
Updating an article (post) or a menu item: instead of deleting the cache of the related page, the entire cache is purged, with loss of performance on the whole website
Updating a module assigned to a single page: instead of deleting the module cache or / and the related page, the entire cache is purged, with loss of performance on the whole website
Updating the Sitemap or even a single Title tag of a page with JSitemap component: why is the entire cache purged?
Setting up or changing a 301 redirect: why is all cache flushed?
These are just some of the cases that come to my mind, the case history is large and the cache is purged improperly following a lot of events such as those described, damaging the performance of the website.
In short, it's not quite what I expected after reading the promises of Litespeed and paying to get it.
A question for Joomla users: do you have the same experience on your websites?
A question for the plugin developers: are you aware of these bugs? Are you working to solve them or do Joomla users have to manage by themselves?
Thanks and regards
I have been using Litespeed Cache for a couple of months and the results are positive for the speed of websites, but not for cache management. The Joomla plugin does not work as it should and the behavior is not that described in the documentation https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscjoomla
"The smart auto-purge feature minimizes cache management needs. No more worrying about synchronization problems. LSCJoomla will detect that you changed an article, you changed a menu setting, or you changed a module setting. Then, it will automatically purge related pages. This gives you the freedom to set a longer cache expiration time and improve visitor experience, confident that the cache will be purged when the relevant content or setting changes."
Updating an article (post) or a menu item: instead of deleting the cache of the related page, the entire cache is purged, with loss of performance on the whole website
![cache content edited.png](https://download.litespeedtech.com/support/forum/data/attachments/1/1852-a7454606a69286687dcbab3d81fedf16.jpg)
Updating a module assigned to a single page: instead of deleting the module cache or / and the related page, the entire cache is purged, with loss of performance on the whole website
![purge cache after saved 1 module.png](https://download.litespeedtech.com/support/forum/data/attachments/1/1854-745157d64c9c8f3dbdd38c71627c645d.jpg)
Updating the Sitemap or even a single Title tag of a page with JSitemap component: why is the entire cache purged?
![cache jsitemap.png](https://download.litespeedtech.com/support/forum/data/attachments/1/1856-982676ac77a5d5a079ac5f60249d3153.jpg)
Setting up or changing a 301 redirect: why is all cache flushed?
These are just some of the cases that come to my mind, the case history is large and the cache is purged improperly following a lot of events such as those described, damaging the performance of the website.
In short, it's not quite what I expected after reading the promises of Litespeed and paying to get it.
A question for Joomla users: do you have the same experience on your websites?
A question for the plugin developers: are you aware of these bugs? Are you working to solve them or do Joomla users have to manage by themselves?
Thanks and regards