Cache Cleaner Front End Notification
Search the forum...
Type to search...
Other Bug Reports questions
Ben Seidel
Ben Seidel
We've been using the CDN for Joomla extension in combination with the Cache Cleaner, and we love the functionality overall. The customizability of the notifications and what you can clear with Cache Cleaner is fantastic.
That said, we do have it set to clear caches on item save,apply,publish,unpublish,archive,trash,delete on front end. This makes the save process noticeably slower as the caches are being cleared, including the CDN cache.
We completely understand why this is a bit slower. However, we had multiple users notice and mention the slower saving. Our suggestion is that when a user saves the article, we should show a clearing caches notice for that user with a progress circle/bar. I believe you already do this for the clear caches button on the back end.
Would that be possible to extend this functionality to save/close articles?
We aren't looking for it to be fancy other than just helping users understand the caches are being cleared and help avoid them from doing a second click on saving the article or closing out prematurely.
It would be great if we could control the wording on this notice as well, but that's not critical for us.
Peter van Westen
ADMIN
Peter van Westen
ADMIN
When saving, the cache is cleared during the pageload.
This is different than when clicking on the button, where the cache cleaning gets triggered by an ajax load (so via javascript without refreshing the page).
This is not doable for the frontend (or backend) when doing a save action.
You might want to see if you can clear certain types of cache via the button only. So those won't get cleared on the frontend save action.
Ben Seidel
Ben Seidel
Darn, that's very unfortunate.
Do you have recommended items to clear for via save instead? The most common content typically updated consists of one of the following:
1) A basic text/image update within the article itself
2) an article updated with content our layout via YOOtheme Pro's Builder
3) A blog post created via EasyBlog
Current settings enabled
Purge Cache
Clear expired items
Purge Update cache - in retrospect this should definitely be set to only via button or No, changing that now. I thought that was a different feature originally as I misread the meaning. I have a feeling this is why it was so slow.
Litespeed - is this specifically litespeed for joomla cache plugin, or just the base lightspeed server caching
CDN cache
Peter van Westen
ADMIN
Peter van Westen
ADMIN
Well, whatever cache needs to be cleared depends on how you have set things up. What cache (Joomla/server/CDN) will make the page that gets edited keep the old version displayed? If you can figure that out, you know what you need to clear (as a minimum) on the frontend.
You probably don't need to "Clear expired items" on frontend.
Ben Seidel
Ben Seidel
Thanks for the suggestion regarding clear expired items.
Litespeed - is this specifically litespeed for joomla cache plugin, or just the base lightspeed server caching?
Peter van Westen
ADMIN
Peter van Westen
ADMIN
Server litespeed.
Ben Seidel
Ben Seidel
Thanks for clarifying.
We have the cache clearing really basic now - see private info for details on our setup and hosting environment. But yet, the cache clearing from front end is still very slow.
Is there anything you or we can do to speed this up to be better experience for users?
Peter van Westen
ADMIN
Peter van Westen
ADMIN
Most probably the Key CDN clearing takes up the time. That needs to do a call to the external server and wait for the response.
Check if it is faster if you disable that in Cache Cleaner....
Ben Seidel
Ben Seidel
Yes, it's drastically faster...closer to 15-25% of the time. Is there anyway that the API clear to the CDN can be sped up?
The CDN clear on the back end seems faster than the front end on-save clear.
Peter van Westen
ADMIN
Peter van Westen
ADMIN
The speed of the API is down to the CDN server itself (and your host and the speed of the connection between them).
The backend can seem faster as the frontend needs to render the frontend page itself too. While clearing the cache via the admin side (via the button) only does the cache cleaning part.
Ben Seidel
Ben Seidel
Thanks for the additional information. We decided to not clear the CDN on every article save/publish/edit, etc. which reduces the need for a speedier CDN clear. Honestly, the CDN clear via API is pretty similar speed to other CDNs like StackPath and other integrated platforms like Sucuri/WP Engine etc., so I don't think we need to investigate further at this point.
Feel free to close this out.
Forum
Cache Cleaner Front End Notification
Ben Seidel
Ben Seidel
That said, we do have it set to clear caches on item save,apply,publish,unpublish,archive,trash,delete on front end. This makes the save process noticeably slower as the caches are being cleared, including the CDN cache.
We completely understand why this is a bit slower. However, we had multiple users notice and mention the slower saving. Our suggestion is that when a user saves the article, we should show a clearing caches notice for that user with a progress circle/bar. I believe you already do this for the clear caches button on the back end.
Would that be possible to extend this functionality to save/close articles?
We aren't looking for it to be fancy other than just helping users understand the caches are being cleared and help avoid them from doing a second click on saving the article or closing out prematurely.
It would be great if we could control the wording on this notice as well, but that's not critical for us.
Peter van Westen
ADMIN
Peter van Westen
ADMIN
This is different than when clicking on the button, where the cache cleaning gets triggered by an ajax load (so via javascript without refreshing the page).
This is not doable for the frontend (or backend) when doing a save action.
You might want to see if you can clear certain types of cache via the button only. So those won't get cleared on the frontend save action.
Please post a rating at the
Joomla! Extensions Directory
Ben Seidel
Ben Seidel
Do you have recommended items to clear for via save instead? The most common content typically updated consists of one of the following:
1) A basic text/image update within the article itself
2) an article updated with content our layout via YOOtheme Pro's Builder
3) A blog post created via EasyBlog
Current settings enabled
Purge Cache
Clear expired items
Purge Update cache - in retrospect this should definitely be set to only via button or No, changing that now. I thought that was a different feature originally as I misread the meaning. I have a feeling this is why it was so slow.
Litespeed - is this specifically litespeed for joomla cache plugin, or just the base lightspeed server caching
CDN cache
Peter van Westen
ADMIN
Peter van Westen
ADMIN
You probably don't need to "Clear expired items" on frontend.
Please post a rating at the
Joomla! Extensions Directory
Ben Seidel
Ben Seidel
Litespeed - is this specifically litespeed for joomla cache plugin, or just the base lightspeed server caching?
Peter van Westen
ADMIN
Peter van Westen
ADMIN
Please post a rating at the
Joomla! Extensions Directory
Ben Seidel
Ben Seidel
We have the cache clearing really basic now - see private info for details on our setup and hosting environment. But yet, the cache clearing from front end is still very slow.
Is there anything you or we can do to speed this up to be better experience for users?
Confidential information:
(hidden)
Peter van Westen
ADMIN
Peter van Westen
ADMIN
Check if it is faster if you disable that in Cache Cleaner....
Please post a rating at the
Joomla! Extensions Directory
Ben Seidel
Ben Seidel
The CDN clear on the back end seems faster than the front end on-save clear.
Peter van Westen
ADMIN
Peter van Westen
ADMIN
The backend can seem faster as the frontend needs to render the frontend page itself too. While clearing the cache via the admin side (via the button) only does the cache cleaning part.
Please post a rating at the
Joomla! Extensions Directory
Ben Seidel
Ben Seidel
Feel free to close this out.
You can only post on this forum if you
log in