{"data":{"id":"ACSD-51120","source":"qpt","sourceRef":"magento/quality-patches@1.1.84","title":"Fixes the issue where GraphQL GET requests cache is not cleared for CMS pages that contain CMS blocks that are updated via a staging update.","categories":["Content","GraphQL"],"components":["magento/module-cms","magento/module-cms-staging"],"origin":"adobe-commerce-support","documentation":{"url":"https://experienceleague.adobe.com/en/docs/commerce-operations/tools/quality-patches-tool/patches-available-in-qpt/v1-1-33/acsd-51120-graphql-get-requests-cache-not-cleared-for-cms-pages","path":"help/tools/quality-patches-tool/patches-available-in-qpt/v1-1-33/acsd-51120-graphql-get-requests-cache-not-cleared-for-cms-pages.md","blobSha":"6369878baa521f8b063f10d07f033b429832ec37","description":"GraphQL GET request cache is not cleared for CMS pages that contain CMS blocks that are updated via a staging update.","stepsToReproduce":"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.","introducedInQpt":"1.1.33","createdFor":["2.4.2-p2"],"documentedRange":"2.3.7 - 2.4.2-p2","scheduledFixRelease":"2.4.7"},"files":[{"package":"magento/magento2-base","constraint":">=2.3.7 <2.4.3","path":"patches/os/ACSD-51120_2.4.2-p2.patch","blobSha":"8db8fea26a5e4f2334c053de28ff7e567c85574b","url":"https://raw.githubusercontent.com/magento/quality-patches/11d565bdde197b9c7bac859a5698e99098b48457/patches/os/ACSD-51120_2.4.2-p2.patch","thirdParty":false,"modifies":[{"path":"vendor/magento/module-cms/Model/ResourceModel/Page/Query/PageIdsList.php","change":"added","package":"magento/module-cms"}],"packages":["magento/module-cms"],"hasTests":false,"applicableVersions":{"magento-community":["2.4.2-p2","2.4.2-p1","2.4.2","2.4.1-p1","2.4.1","2.4.0-p1","2.4.0","2.3.7-p4","2.3.7-p3","2.3.7-p2","2.3.7-p1","2.3.7"],"magento-commerce":["2.4.2-p2","2.4.2-p1","2.4.2","2.4.1-p1","2.4.1","2.4.0-p1","2.4.0","2.3.7-p4","2.3.7-p3","2.3.7-p2","2.3.7-p1","2.3.7"],"mage-os":[]},"unknownVersions":[],"requires":[],"replacedWith":null,"deprecated":false},{"package":"magento/magento2-ee-base","constraint":">=2.3.7 <2.4.3","path":"patches/commerce/ACSD-51120_2.4.2-p2.patch","blobSha":"5e1beb7e795c823438b52d87b0f9c830939dcd41","url":"https://raw.githubusercontent.com/magento/quality-patches/11d565bdde197b9c7bac859a5698e99098b48457/patches/commerce/ACSD-51120_2.4.2-p2.patch","thirdParty":false,"modifies":[{"path":"vendor/magento/module-cms-staging/Model/BlockApplier.php","change":"added","package":"magento/module-cms-staging"},{"path":"vendor/magento/module-cms-staging/etc/di.xml","change":"modified","package":"magento/module-cms-staging"}],"packages":["magento/module-cms-staging"],"hasTests":false,"applicableVersions":{"magento-community":[],"magento-commerce":["2.4.2-p2","2.4.2-p1","2.4.2","2.4.1-p1","2.4.1","2.4.0-p1","2.4.0","2.3.7-p4","2.3.7-p3","2.3.7-p2","2.3.7-p1","2.3.7"],"mage-os":[]},"unknownVersions":[],"requires":[],"replacedWith":null,"deprecated":false}],"applicableVersions":{"magento-community":["2.4.2-p2","2.4.2-p1","2.4.2","2.4.1-p1","2.4.1","2.4.0-p1","2.4.0","2.3.7-p4","2.3.7-p3","2.3.7-p2","2.3.7-p1","2.3.7"],"magento-commerce":["2.4.2-p2","2.4.2-p1","2.4.2","2.4.1-p1","2.4.1","2.4.0-p1","2.4.0","2.3.7-p4","2.3.7-p3","2.3.7-p2","2.3.7-p1","2.3.7"],"mage-os":[]},"conditions":null,"requirements":null},"_documentation":"https://magento.watch/api","_description":"Quality patch ACSD-51120 details"}