Feature #81560
closedAdd cache-clearing for mod_pagespeed
0%
Description
It it possible to clear the full cache (first step) or individual parts. We should at least have something in place that tries to flush the cache upon a "clear all caches".
https://modpagespeed.com/doc/system#flush_cache
Note: With cache-busting URLs (timestamp in URL) for things like CSS-files there won't be a problem since "new URLs" are used if those files change.
Updated by Benni Mack about 5 years ago
- Status changed from New to Needs Feedback
Hey Stefan,
can you elaborate what is missing here in TYPO3? Don't really get your point unfortunately...
Updated by Stefan Neufeind about 5 years ago
If mod_pagespeed is loaded and content on the site (or in JS/CSS changes) it would help to inform pagespeed so it can re-generate minimized JS/CSS-files or the like. There are functions that can be called. If we don't want to selectively clear the cache we could at least flush pagespeed completely imho. Like with opcache we could detect if pagespeed is loaded and if so flush caches.
Updated by Riccardo De Contardi almost 5 years ago
- Status changed from Needs Feedback to New
Updated by Susanne Moog over 4 years ago
- Status changed from New to Needs Feedback
For me there's a difference between opcache (and others) basically provided by PHP itself and third-party caching modules like mod_pagespeed.
IMHO we should not provide a core solution here but rather someone could go ahead and build a corresponding extension. Similar to what you'd do if you have varnish and need to tell it to re-fetch pages.
Updated by Riccardo De Contardi over 3 years ago
- Status changed from Needs Feedback to Closed
As Susanne Moog already wrote, the support for this kind of features should be better added via an extension, like the support for Varnish.
I therefore close this request; if you think that this is the wrong decision, please reopen it or ping me.
In my opinion, TYPO3 core cannot provide support for each existing caching module, and "official" support for a limited list of those would require discussion and people that will mantain the code inside the core.
Maybe a discussion on the topic could be started on the Slack TYPO3 platform?