Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magento unable to fully read themes [Magento 2.0.5] #4445

Closed
AngelsDustz opened this issue May 10, 2016 · 6 comments
Closed

Magento unable to fully read themes [Magento 2.0.5] #4445

AngelsDustz opened this issue May 10, 2016 · 6 comments
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: needs update

Comments

@AngelsDustz
Copy link

Steps to reproduce

  1. Create a new theme in app/design/frontend/[Vendor]/[Theme]
  2. Create a layout.xml and theme.xml
    3.
    a. When trying to select your theme in Page->Theme you will get the default Theme name
    b. When trying to select a layout from your theme in Content->page you are only able to select the default layouts.

Expected result

  1. Create the files, configure them and select and use them.

Actual result

  1. The Theme will get default values. (theme.xml and layout.xml not being read)
    (The theme does get detected though!)
  2. The Theme has no layouts.

I managed to fix this by reverting to version 2.0.0
During all of this I tried any thing I could to get it to work;

  • reset cache
  • edit vendor files (This actually gave some results, but really weird ones)

During all this the Mode was set to development.

If anything this needs some research.

@mazhalai
Copy link
Contributor

@AngelsDustz this looks like the duplicate of #2797

@AngelsDustz
Copy link
Author

@mazhalai By the looks of it (s)he wants to include/load a Theme using composer as where I tried to create one.
Also my themes were added, it simply didn't read beyond the fact it saw the folder, theme.xml etc. was being ignored.

@mazhalai mazhalai self-assigned this May 11, 2016
@mazhalai
Copy link
Contributor

@AngelsDustz did you have a chance to try it on 2.1.0-rc1?

@AngelsDustz
Copy link
Author

@mazhalai Sorry I didn't after we saw it didn't work/gave problems on 2.0.5
we reverted back to 2.0.0 A.S.A.P.

@mazhalai
Copy link
Contributor

@AngelsDustz regardless, we have created MAGETWO-53544 to investigate.

@mazhalai mazhalai added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development CS and removed PS labels May 27, 2016
@mazhalai mazhalai removed their assignment May 27, 2016
@skovalenk
Copy link
Contributor

Hi @AngelsDustz
I have checked MAGETWO-53544 on Magento 2.1.0-rc.
Seems problem was fixed. This bug was also related to this one: #519

@slavvka slavvka closed this as completed Jun 1, 2016
magento-engcom-team pushed a commit that referenced this issue Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: needs update
Projects
None yet
Development

No branches or pull requests

5 participants