3

I did a fresh setup of magento2 and upon completion, I couldn't set any configuration options in Content > Design > Configuration. The table rendered with no available results.

After trying numerous troubleshooting steps, I finally deleted my custom theme out of the app/design/frontend/vendor/template folder. Once app/design/frontend/ only contained the Magento folder and nothing else, the install properly set a default configuration for the stores and the Content > Design > Configuration renders perfectly normal. I am then able to copy my custom theme back into the frontend design folder and set it as active.

Apparently, Magento2 completely falls apart and can't set the default Luma theme if you have theme files installed. Has anyone else encountered this bug? Could there be something in my custom theme that causes a fresh install to fail when setting the default theme?

  • How you create a new theme? – Khoa TruongDinh Dec 11 '16 at 0:48
  • I followed the file structure example from the dev docs here: devdocs.magento.com/guides/v2.1/frontend-dev-guide/themes/… I set mine to extend Magento/luma – David Stillson Dec 12 '16 at 20:49
  • old post I know - but did you ever find a solution? suffering same thing :S – treyBake Nov 15 '17 at 16:47
  • @ThisGuyHasTwoThumbs I think I had to completely remove the custom theme, perform the setup, and then add the theme folder back in afterward. – David Stillson Nov 16 '17 at 18:28
  • @DavidStillson I tried that and weirdly still an issue on Magento 2.2.1 :S but no worries will do some debugging, if I find a solution will let you know! Thanks anyways :) – treyBake Nov 17 '17 at 9:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.