ACSD-51120: GraphQL GET request cache is not cleared for CMS pages that contain CMS blocks…

Categories

Content, GraphQL

Components

magento/module-cms, magento/module-cms-staging

Origin

adobe-commerce-support

Since QPT

1.1.33

Issue

GraphQL GET request cache is not cleared for CMS pages that contain CMS blocks that are updated via a staging update.

Steps to reproduce

1. Create a CMS block. 1. Include the CMS block into a CMS page using the Page Builder. 1. Fetch the CMS page using the given GraphQL query using a GET request: { cmsPage( identifier: "<CMS PAGE IDENTIFIER>") { content content_heading identifier meta_description meta_keywords meta_title page_layout title url_key } } 1. Make sure the GraphQL response is cached in Varnish. 1. Create a scheduled update for the block. 1. Wait for the scheduled update to apply and run the cron job to apply the scheduled update. 1. Fetch the CMS page again using the given GraphQL query using a GET request.

Adobe's page lists 2.3.7 - 2.4.2-p2 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.4.7.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACSD-51120. On Cloud, add ACSD-51120 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACSD-51120/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.

Patch files and compatible versions

Sources

• Adobe documentation for ACSD-51120
• JSON API: /api/v1/patches/ACSD-51120