Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am not sure how much support this repository and branch still gets - so feel free to ignore :)
Currently when editing a record in the back end, the HTTP cache is not cleared, since no cache tags are added in the front end.
Let's say you have a table called
foobarin Catalog Manager. When you edit something in the back end, Contao will automatically clear the cache for the following tags:contao.db.foobarcontao.db.foobar.42(with 42 being the ID of the edited record)This PR adds the following cache tags:
contao.db.foobarin the list view - so when a record gets edited, all list views of that table get cleared from the cache.contao.db.foobar.42in the detail view - so when a record gets edited, the detail URL of that record gets cleared from the cache.