ACSD-48634: [!DNL JS] errors when [!DNL Google Analytics Content Experiments] enabled

The ACSD-48634 patch fixes [!DNL JS] errors on a [!DNL staging] update page when [!DNL Google Analytics Content Experiments] is enabled. This patch is available when the [!DNL Quality Patches Tool (QPT)] 1.1.27 is installed. The patch ID is ACSD-48634. Please note that the issue was fixed in Adobe Commerce 2.4.7.

Affected products and versions

The patch is created for Adobe Commerce version:

• Adobe Commerce (all deployment methods) 2.4.5

Compatible with Adobe Commerce versions:

• Adobe Commerce (all deployment methods) 2.3.7 - 2.4.6

Issue

[!DNL JS] errors occur on a [!DNL staging] update page when [!DNL Google Analytics Content Experiments] is enabled.

Steps to reproduce:

1. In [!UICONTROL Admin] > [!UICONTROL Stores] > [!UICONTROL All Stores], create an additional website, store, and [!UICONTROL Store View]. Make sure the [!UICONTROL Store View] is [!UICONTROL Enabled].
2. Configure [!DNL Configure Google Analytics] by going to [!UICONTROL Stores] > [!UICONTROL Settings] > [!UICONTROL Configuration] > [!UICONTROL Sales] > [!UICONTROL Google API]:
   • For [!DNL Main] and additional websites [!DNL scope]:
     • [!UICONTROL Enabled]: [!UICONTROL Yes]
     • [!UICONTROL Account type]: [!UICONTROL Google Tag Manager]
     • [!UICONTROL Anonymize IP]: [!UICONTROL Yes]
     • [!UICONTROL Enable Content Experiments]: [!UICONTROL Yes]
     • [!UICONTROL Container Id]: [!UICONTROL (GTM container ID)]
     • [!DNL Uncheck] [!UICONTROL Use Default] for other fields, but do not change them.
   • For [!DNL Default Config] [!DNL scope]:
     • [!UICONTROL Enabled]: [!UICONTROL Yes]
     • [!UICONTROL Account type]: [!UICONTROL Universal Analytics]
     • [!UICONTROL Account Number]: [!UICONTROL (Universal Analytics account number)]
     • [!UICONTROL Anonymize IP]: [!UICONTROL Yes]
     • [!UICONTROL Enable Content Experiments]: [!UICONTROL Yes]
3. Disable [!DNL Configure Google Analytics] on [!DNL Default Config] [!DNL scope] by changing [!UICONTROL Enable] from [!UICONTROL Yes] to [!UICONTROL No]. Make sure not to change anything else!
4. Go to [!UICONTROL Catalog] > [!UICONTROL Categories].
5. Create and Edit any [!UICONTROL category] and add a scheduled update for it:
   • Any name, start date in the future, end date in the future, and any change in [!UICONTROL category] ([!UICONTROL For Example]: [!UICONTROL disable category]).
6. Save the update and check the [!DNL browser developer console] for errors.

Expected results:

No [!DNL JS] errors and the changes to the [!DNL staging] update are saved successfully.

Actual results:

[!DNL JS] errors are visible in the console, the form is malformed, and the [!DNL spinner] never gets disabled after the save.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

• Adobe Commerce or Magento Open Source on-premises: [!DNL Quality Patches Tool] > Usage in the [!DNL Quality Patches Tool] guide.
• Adobe Commerce on cloud infrastructure: Upgrades and Patches > Apply Patches in the Commerce on Cloud Infrastructure guide.

Related reading

To learn more about [!DNL Quality Patches Tool], refer to:

• [!DNL Quality Patches Tool] released: a new tool to self-serve quality patches in our support knowledge base.
• Check if patch is available for your Adobe Commerce issue using [!DNL Quality Patches Tool] in our support knowledge base.

For info about other patches available in QPT, refer to [!DNL Quality Patches Tool]: Search for patches in the [!DNL Quality Patches Tool] guide.