Something went wrong while saving this configuration: Area is already set












22















I am unable to apply a new theme in a clean install of 2.2.4. Upading to 2.2.5 does not fix the problem.










share|improve this question

























  • could please share with me what have you actually done

    – hweb87
    May 11 '18 at 11:26
















22















I am unable to apply a new theme in a clean install of 2.2.4. Upading to 2.2.5 does not fix the problem.










share|improve this question

























  • could please share with me what have you actually done

    – hweb87
    May 11 '18 at 11:26














22












22








22


5






I am unable to apply a new theme in a clean install of 2.2.4. Upading to 2.2.5 does not fix the problem.










share|improve this question
















I am unable to apply a new theme in a clean install of 2.2.4. Upading to 2.2.5 does not fix the problem.







theme magento2.2.4






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 17 '18 at 8:37









Dan

1,066723




1,066723










asked May 11 '18 at 11:11









Ankush VermaAnkush Verma

1291110




1291110













  • could please share with me what have you actually done

    – hweb87
    May 11 '18 at 11:26



















  • could please share with me what have you actually done

    – hweb87
    May 11 '18 at 11:26

















could please share with me what have you actually done

– hweb87
May 11 '18 at 11:26





could please share with me what have you actually done

– hweb87
May 11 '18 at 11:26










2 Answers
2






active

oldest

votes


















48














Note : This is a know issue in Magento 2.2.4 (see GitHub issue) and below fix is just a temp fix. You should not directly change the Magento core file (override or create a plugin)



Change in MagentoEmailModelAbstractTemplate.php this:



public function setForcedArea($templateId)
{
if ($this->area) {
throw new LogicException(__('Area is already set'));
}
$this->area = $this->emailConfig->getTemplateArea($templateId);
return $this;
}


For this:



public function setForcedArea($templateId)
{
if (!isset($this->area)) {
$this->area = $this->emailConfig->getTemplateArea($templateId);
}
return $this;
}


It should fix the issue



Update : can also be fixed by applying this Patch






share|improve this answer





















  • 3





    Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

    – eskaliert
    May 13 '18 at 13:03








  • 2





    It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

    – Alaksandar Jesus Gene
    May 23 '18 at 13:10








  • 2





    Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

    – Swapnil Tatkondawar
    Aug 28 '18 at 11:39






  • 2





    Issue resolved in Magento2.2.6

    – Manish Maheshwari
    Sep 19 '18 at 11:53






  • 1





    Thanks for updating your answer with the link to the patch file :)

    – Jonathan Marzullo
    Oct 8 '18 at 15:36



















0














Hello @SwapnilTatkondawar, As per your instructions i have D/L the patch... but where do i install it on my IDE before running the said command?



Thank you,






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "479"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f225628%2fsomething-went-wrong-while-saving-this-configuration-area-is-already-set%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    48














    Note : This is a know issue in Magento 2.2.4 (see GitHub issue) and below fix is just a temp fix. You should not directly change the Magento core file (override or create a plugin)



    Change in MagentoEmailModelAbstractTemplate.php this:



    public function setForcedArea($templateId)
    {
    if ($this->area) {
    throw new LogicException(__('Area is already set'));
    }
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    return $this;
    }


    For this:



    public function setForcedArea($templateId)
    {
    if (!isset($this->area)) {
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    }
    return $this;
    }


    It should fix the issue



    Update : can also be fixed by applying this Patch






    share|improve this answer





















    • 3





      Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

      – eskaliert
      May 13 '18 at 13:03








    • 2





      It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

      – Alaksandar Jesus Gene
      May 23 '18 at 13:10








    • 2





      Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

      – Swapnil Tatkondawar
      Aug 28 '18 at 11:39






    • 2





      Issue resolved in Magento2.2.6

      – Manish Maheshwari
      Sep 19 '18 at 11:53






    • 1





      Thanks for updating your answer with the link to the patch file :)

      – Jonathan Marzullo
      Oct 8 '18 at 15:36
















    48














    Note : This is a know issue in Magento 2.2.4 (see GitHub issue) and below fix is just a temp fix. You should not directly change the Magento core file (override or create a plugin)



    Change in MagentoEmailModelAbstractTemplate.php this:



    public function setForcedArea($templateId)
    {
    if ($this->area) {
    throw new LogicException(__('Area is already set'));
    }
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    return $this;
    }


    For this:



    public function setForcedArea($templateId)
    {
    if (!isset($this->area)) {
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    }
    return $this;
    }


    It should fix the issue



    Update : can also be fixed by applying this Patch






    share|improve this answer





















    • 3





      Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

      – eskaliert
      May 13 '18 at 13:03








    • 2





      It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

      – Alaksandar Jesus Gene
      May 23 '18 at 13:10








    • 2





      Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

      – Swapnil Tatkondawar
      Aug 28 '18 at 11:39






    • 2





      Issue resolved in Magento2.2.6

      – Manish Maheshwari
      Sep 19 '18 at 11:53






    • 1





      Thanks for updating your answer with the link to the patch file :)

      – Jonathan Marzullo
      Oct 8 '18 at 15:36














    48












    48








    48







    Note : This is a know issue in Magento 2.2.4 (see GitHub issue) and below fix is just a temp fix. You should not directly change the Magento core file (override or create a plugin)



    Change in MagentoEmailModelAbstractTemplate.php this:



    public function setForcedArea($templateId)
    {
    if ($this->area) {
    throw new LogicException(__('Area is already set'));
    }
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    return $this;
    }


    For this:



    public function setForcedArea($templateId)
    {
    if (!isset($this->area)) {
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    }
    return $this;
    }


    It should fix the issue



    Update : can also be fixed by applying this Patch






    share|improve this answer















    Note : This is a know issue in Magento 2.2.4 (see GitHub issue) and below fix is just a temp fix. You should not directly change the Magento core file (override or create a plugin)



    Change in MagentoEmailModelAbstractTemplate.php this:



    public function setForcedArea($templateId)
    {
    if ($this->area) {
    throw new LogicException(__('Area is already set'));
    }
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    return $this;
    }


    For this:



    public function setForcedArea($templateId)
    {
    if (!isset($this->area)) {
    $this->area = $this->emailConfig->getTemplateArea($templateId);
    }
    return $this;
    }


    It should fix the issue



    Update : can also be fixed by applying this Patch







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Aug 28 '18 at 16:40

























    answered May 11 '18 at 11:28









    Vishwas BhatnagarVishwas Bhatnagar

    2,80721945




    2,80721945








    • 3





      Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

      – eskaliert
      May 13 '18 at 13:03








    • 2





      It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

      – Alaksandar Jesus Gene
      May 23 '18 at 13:10








    • 2





      Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

      – Swapnil Tatkondawar
      Aug 28 '18 at 11:39






    • 2





      Issue resolved in Magento2.2.6

      – Manish Maheshwari
      Sep 19 '18 at 11:53






    • 1





      Thanks for updating your answer with the link to the patch file :)

      – Jonathan Marzullo
      Oct 8 '18 at 15:36














    • 3





      Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

      – eskaliert
      May 13 '18 at 13:03








    • 2





      It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

      – Alaksandar Jesus Gene
      May 23 '18 at 13:10








    • 2





      Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

      – Swapnil Tatkondawar
      Aug 28 '18 at 11:39






    • 2





      Issue resolved in Magento2.2.6

      – Manish Maheshwari
      Sep 19 '18 at 11:53






    • 1





      Thanks for updating your answer with the link to the patch file :)

      – Jonathan Marzullo
      Oct 8 '18 at 15:36








    3




    3





    Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

    – eskaliert
    May 13 '18 at 13:03







    Thanks! This has solved my issue. To reproduce: In Content > Design > Configuration > "Edit" your theme on Store View Level. If you do any change (no matter if applying a theme or changing a logo) the following message pops up: "Something went wrong while saving this configuration: Area is already set [on hold]".

    – eskaliert
    May 13 '18 at 13:03






    2




    2





    It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

    – Alaksandar Jesus Gene
    May 23 '18 at 13:10







    It worked as i edited in core file. How to override this specifc model file so i dont edit any core file. What is the folder structure i need to use in app folder.

    – Alaksandar Jesus Gene
    May 23 '18 at 13:10






    2




    2





    Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

    – Swapnil Tatkondawar
    Aug 28 '18 at 11:39





    Magento 2 doesn't do hotfix releases, unfortunately. However, they've released an official patch over here: magento.com/tech-resources/download (search for MAGETWO-93036). Apply this patch by using below command patch -p1 < m2-hotfixes/EE-MAGETWO-93036-2018-07-02-07-07-16.patch. After applying mention patch and It works perfectly.

    – Swapnil Tatkondawar
    Aug 28 '18 at 11:39




    2




    2





    Issue resolved in Magento2.2.6

    – Manish Maheshwari
    Sep 19 '18 at 11:53





    Issue resolved in Magento2.2.6

    – Manish Maheshwari
    Sep 19 '18 at 11:53




    1




    1





    Thanks for updating your answer with the link to the patch file :)

    – Jonathan Marzullo
    Oct 8 '18 at 15:36





    Thanks for updating your answer with the link to the patch file :)

    – Jonathan Marzullo
    Oct 8 '18 at 15:36













    0














    Hello @SwapnilTatkondawar, As per your instructions i have D/L the patch... but where do i install it on my IDE before running the said command?



    Thank you,






    share|improve this answer




























      0














      Hello @SwapnilTatkondawar, As per your instructions i have D/L the patch... but where do i install it on my IDE before running the said command?



      Thank you,






      share|improve this answer


























        0












        0








        0







        Hello @SwapnilTatkondawar, As per your instructions i have D/L the patch... but where do i install it on my IDE before running the said command?



        Thank you,






        share|improve this answer













        Hello @SwapnilTatkondawar, As per your instructions i have D/L the patch... but where do i install it on my IDE before running the said command?



        Thank you,







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 10 mins ago









        rav narayanrav narayan

        136




        136






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Magento Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f225628%2fsomething-went-wrong-while-saving-this-configuration-area-is-already-set%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            What other Star Trek series did the main TNG cast show up in?

            Berlina muro

            Berlina aerponto