Bug #103804
open
Site configuration changes don't trigger cache flushes
Added by Patrick Schriner 2 months ago.
Updated 2 months ago.
Description
Site configuration changes don't any events, as we are missing the SiteConfigurationChangedEvent event.
For a distributed TYPO3 installation I want to be able to send site configuration changes to other instances, or clear the frontend cache if needed
- Status changed from New to Under Review
SiteConfigurationChangedEvent was added in v13 as internal event to be able to invalidate runtime caches in https://review.typo3.org/c/Packages/TYPO3.CMS/+/83557
This is not intended as public API.
Your usecase – multiinstance cache-coordination – should be implemented using a custom cache-backend.
You can overwrite the `cache.core` Backend and then signal other instances that way.
- Status changed from Under Review to Rejected
Benjamin Franzke wrote in #note-4:
SiteConfigurationChangedEvent was added in v13 as internal event to be able to invalidate runtime caches in https://review.typo3.org/c/Packages/TYPO3.CMS/+/83557
This is not intended as public API.
Your usecase – multiinstance cache-coordination – should be implemented using a custom cache-backend.
You can overwrite the `cache.core` Backend and then signal other instances that way.
Thanks for the direction
- Status changed from Rejected to Under Review
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by