- Issue created by @Hydra
- Merge request !31#3485486 Collect all cacheable metadata when building the slot block. → (Merged) created by Hydra
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
Since slot's can use conditions which requires their own caching machanisms to be respected, it sometimes can happen that invalidating for the slot cache tag will not be enough. A simple example would be a request path condition.
- Add a slot to a default layout
- Create a block and configure the slot to use the new slot
- Add a second condition "request path" and limit the content to be shown on just one path of the route you added the slot to
- Now first load a path where the content should not be displayed
- Now load the configured path
The result will be empty since the slot has been cached empty and the path.url cache context from the request path condition will have no effect.
Collect all cache metadata from all conditions when building the slot block.
Needs review
1.0
Code
Automatically closed - issue fixed for 2 weeks with no activity.