Cache metadata of individual blocks are not taken into account when rendering blocks in quicktabs

Created on 28 September 2023, over 1 year ago

Problem/Motivation

Steps to reproduce

- Create a custom block programatically. Let's call it `CustomBlock`.
- Add `getCacheTags()` method to it and set some cache tags.
- Use this block in quicktab.
- Verify if the quicktab block contains the cache tags of `CustomBlock`. This can be verified from the `cache_render` table where `cid` column will contain the id of the quicktab block.
- It will be seen those cache tags are not present.

This causes problem with cache invalidity.

Proposed resolution

Consider the cache metadata set at block level and merge it to the cache metadata of the quicktab block.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Active

Version

3.0

Component

Code

Created by

🇮🇳India Vivek Panicker Kolkata

Live updates comments and jobs are added and updated live.

Merge Requests

!31Cache metadata of individual blocks are not taken into account when rendering blocks in quicktabs
Open
🇮🇳India kumareshbaksi
updated 24 days ago

Comments & Activities

Issue created by @Vivek Panicker
Comment over 1 year ago →
🇮🇳India Vivek Panicker Kolkata
Comment about 1 month ago →
🇺🇸United States smustgrave
First commit to issue fork.
Merge request !31Issue #3390465: Fixed the cache metadata of individual blocks are not taken into account when rendering block s in quicktabs. → (Open) created by kumareshbaksi
Pipeline finished with Success
24 days ago
Total: 228s
#379573
Pipeline finished with Success
24 days ago
Total: 176s
#379575
Comment 24 days ago →
🇮🇳India kumareshbaksi
@vivek I have raised the MR.
I have added the cache tags in the render array from plugin_block.
Please check.
Comment 12 days ago →
🇺🇸United States smustgrave

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024