Currently, the ViewsBlockBase class does not fully leverage the cache metadata (contexts, tags, max-age) provided by the associated view's display handler. This can lead to inconsistencies in cache behavior when using Views blocks, especially when the display handler defines specific cache settings.
For example:
This limits the ability to align the block's caching behavior with that of the View, potentially resulting in outdated content being served or inefficient cache invalidation.
1. Create a View with specific cache metadata in its display handler (e.g., cache contexts or tags).
2. Add the View as a block on a page.
3. Observe that the cache behavior of the block does not reflect the settings in the display handler.
Introduce overrides in the ViewsBlockBase class for the following methods:
getCacheContexts()getCacheTags()getCacheMaxAge()These methods will merge the cache metadata from the parent block class with the cache metadata from the view's display handler, ensuring consistent and efficient caching.
None.
None.
No API changes. The modifications enhance the existing methods without altering their signatures or introducing breaking changes.
None.
The ViewsBlockBase class now merges cache metadata from the associated view's display handler for contexts, tags, and max-age. This ensures consistent cache behavior between Views blocks and their display handlers.
Active
11.1 🔥
views.module
Is this maybe trying to fix the same problem as #2632828: Block view cachability metadata doesn't get copied in BlockView::preRender() when the block content is non-empty → ? Not sure, but feel very similar.
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .