Project

General

Profile

Actions
Copy link

Bug #103804

open

Site configuration changes don't trigger cache flushes

Added by Patrick Schriner 2 months ago. Updated 2 months ago.

Status:
Under Review
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2024-05-08
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:

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

Actions
Copy link
 #1

Updated by Gerrit Code Review 2 months ago

  • Status changed from New to Under Review

Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/84178

Actions
Copy link
 #2

Updated by Gerrit Code Review 2 months ago

Patch set 2 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/84178

Actions
Copy link
 #3

Updated by Gerrit Code Review 2 months ago

Patch set 3 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/84178

Actions
Copy link
 #4

Updated by Benjamin Franzke 2 months ago

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.

Actions
Copy link
 #5

Updated by Benjamin Franzke 2 months ago

  • Status changed from Under Review to Rejected
Actions
Copy link
 #6

Updated by Patrick Schriner 2 months ago

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

Actions
Copy link
 #7

Updated by Gerrit Code Review 2 months ago

  • Status changed from Rejected to Under Review

Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/84185

Actions
Copy link
 #8

Updated by Gerrit Code Review 2 months ago

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/84185

Actions
Copy link
 #9

Updated by Gerrit Code Review 2 months ago

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/84185

Actions
Copy link

Also available in: Atom PDF