#103804Site configuration changes don't trigger cache flushes
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
Reviews 3
History 411
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 84178 status
NewUnder Review <span data-processor="relativetime" data-value="2024-05-08T09:32:17+00:00" > 05/08/24, 09:32 </span> -
Gerrit Code Review pushed patch set 2 for 12.4 to change 84178 <span data-processor="relativetime" data-value="2024-05-08T09:33:55+00:00" > 05/08/24, 09:33 </span>
-
Gerrit Code Review pushed patch set 3 for 12.4 to change 84178 <span data-processor="relativetime" data-value="2024-05-08T09:35:23+00:00" > 05/08/24, 09:35 </span>
-
Benjamin Franzke commented <span data-processor="relativetime" data-value="2024-05-08T09:48:55+00:00" > 05/08/24, 09:48 </span>
-
Benjamin Franzke changed status
Under ReviewRejected <span data-processor="relativetime" data-value="2024-05-08T09:49:05+00:00" > 05/08/24, 09:49 </span> -
Patrick Schriner commented <span data-processor="relativetime" data-value="2024-05-08T09:53:03+00:00" > 05/08/24, 09:53 </span>
Benjamin Franzke wrote in #note-4:
>SiteConfigurationChangedEventwas added in v13 asinternalevent 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
-
Gerrit Code Review pushed patch set 1 for main to change 84185 status
RejectedUnder Review <span data-processor="relativetime" data-value="2024-05-10T06:09:54+00:00" > 05/10/24, 06:09 </span> -
Gerrit Code Review pushed patch set 2 for main to change 84185 <span data-processor="relativetime" data-value="2024-05-10T09:05:03+00:00" > 05/10/24, 09:05 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 84185 <span data-processor="relativetime" data-value="2024-05-10T09:58:07+00:00" > 05/10/24, 09:58 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 84185 <span data-processor="relativetime" data-value="2024-10-18T13:30:50+00:00" > 10/18/24, 13:30 </span>
-
Georg Ringer commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2025-04-10T19:58:17+00:00" > 04/10/25, 19:58 </span>closing the issue as patch on gerrit has been abandoned and a valid solution presented in comments
SiteConfigurationChangedEventwas added in v13 asinternalevent to be able to invalidate runtime caches in https://review.typo3.org/c/Packages/TYPO3.CMS/+/83557This 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.