This article provides a patch for the known Magento Commerce (Cloud) 2.2.4 issue related to getting the "Area is already set" error message when trying to set a theme for the Default Store View in the Magento Admin.
You get the "Something went wrong while saving this configuration: Area is already set" error message when trying to set a theme for the Default Store View.
Steps to reproduce:
- Log in to Magento Admin.
- Navigate to Content>Design>Configuration.
- Set the configuration scope to Default Store View.
- Change the theme in the Applied Theme drop-down. For example, from Magento Luma to Magento Blank.
- Click Save Configuration.
The selected theme is applied for the default store view.
Theme is not applied, the "Something went wrong while saving this configuration: Area is already set" error message is displayed.
The patch is attached to this article. To download it, click the following link or scroll down to the end of the article and click the attached file:
Compatible Magento versions:
The patch was created for:
- Magento Commerce (Cloud) 2.2.4
The patch is also compatible (but might not solve the issue) with the following Magento versions and editions:
- Magento Commerce (Cloud) 2.0.X
- Magento Commerce (Cloud) 2.1.X
- Magento Commerce (Cloud) from 2.2.0 to 2.2.5
- Magento Commerce 2.0.X
- Magento Commerce 2.1.X
- Magento Commerce from 2.2.0 to 2.2.5
How to apply the patch
We strongly recommend applying and testing the patch on the Integration/Staging environment, before applying it Production. We also recommend to have a recent backup before any manipulations.
How to apply this patch for Magento Commerce (Cloud)
(replace the patch name with a particular one)
- If you do not have a directory named
m2-hotfixesin the project root, please create one.
- Copy the
MDVA-11106_EE_2.2.4_v1.composer.patchfile(s) to the
Add, commit, and push your code changes:
git add -A && git commit -m "Apply MDVA-11106_EE_2.2.4_v1 patch" && git push origin
How to apply this patch for Magento Commerce
- Upload the patch to your Magento root directory.
- Run the following SSH command:
(If the above command does not work, try using
patch -p1 < MDVA-11106_EE_2.2.4_v1.composer.patch
- For the changes to be reflected, refresh the cache in the Admin under System > Cache Management.