You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
It would be a great feature if the cache would be improved in the future version of TL. Mainly, I would see these new features, ordered in increasing difficulty to implement :
cache automatically flushed when updating a content (that's the minimum
possibility to flush the cache of a specific page
separate caching for frontend-modules (no more need to flush all the cache when the lastest news change on the website and when this news appears on all pages))
Please see also this forum thread for some thoughts about automatically flushing the cache files for modified pages (points 1 and 2). Best regards, Georg
--- Originally created by deerwood on November 28th, 2009, at 05:41am
Now that Google officially have announced that page speed now is one of the about 200 ranking factors (http://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html) i finds this a bit critical - its also pretty difficult to explain to clients how and why nothing is updated on their website until they manually have purged the cache .. i finds my self even disabling page caching for some of my clients because its just too complicated especially when they have multiple registered users who can edit their own personal profiles ..
So automated cache flushing based on content editing would be really really great :)
--- Originally created by JimmyRittenborg on April 13th, 2010, at 05:34pm
It would be a great feature if the cache would be improved in the future version of TL. Mainly, I would see these new features, ordered in increasing difficulty to implement :
Related issues: #1683
--- Originally created by cbadoud on November 26th, 2009, at 05:41am (ID 1206)
The text was updated successfully, but these errors were encountered: