Description
Preconditions and environment
For Magento 2.4.7 multi-store implementations with the patch ACSD-62591 installed, the FPC is working. However, the naming convention of the Cache Keys does not seem to follow the pattern of Magento versions prior to 2.4.7.
Steps to reproduce
- A Magento 2.4.7 multi-store implementation where the visitor is directed to the appropriate store via Apache .htaccess directives such as the following ones:
SetEnvIf Host www\.dlastore\.com MAGE_RUN_CODE=default
SetEnvIf Host www\.dlastore\.com MAGE_RUN_TYPE=store
SetEnvIf Host fr\.dlastore\.com MAGE_RUN_CODE=french_dla
SetEnvIf Host fr\.dlastore\.com MAGE_RUN_TYPE=store
- The patch ACSD-62591 should be installed.
- Visit a page of the store
Expected result
The name of the Cache Key for FPC should include the values of the environment variables MAGE_RUN_TYPE and MAGE_RUN_CODE. I provide below the Vary Data from a 3rd party module which shows the IDs of the FPC Cache Keys on Magento 2.4.6:
Actual result
The name of the Cache Key for FPC does not include the values of the environment parameters variables MAGE_RUN_TYPE and MAGE_RUN_CODE. I provide below the Vary Data from a 3rd party module which shows the IDs of the FPC Cache Keys on Magento 2.4.7:
Additional information
No response
Release note
No response
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status