-
Notifications
You must be signed in to change notification settings - Fork 102
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
Custom theme couldn't be detected #1517
Comments
Hi @webcreative24. Thank you for your report. Join Magento Community Engineering Slack and ask your questions in #github channel. |
@magento I am working on this |
Hi @webcreative24! 👋 |
@magento add to contributors team |
Hi @webcreative24! 👋 |
@magento I am working on this |
Hello @VitaliyBoyko It seems that now the theme should start with a lowercase letter The documentation does not say that the theme should start with a lowercase letter, it just uses the But there is such a note:
Thanks! |
Thanks @DmitryFurs I'll check the 'frontend/Vendor/Theme' case. |
'frontend/vendor/theme' is also a possible case and needs to be covered as well. Little too much freedom, I would say 😄 |
ok so here is the current version committed This should be the updated? Or will this be allowing any valid folder/file character? |
Describe the bug (*)
I've created a custom theme in the following folder: app/design/frontend/Vendor/custom-theme. Everything works fine but Magento PHPStorm plugin cannot detect the custom theme when I tried to override core module template
The problem occurs that there is a dash in my custom theme name
To Reproduce (*)
Steps to reproduce the behavior:
Expected behavior (*)
The Target theme dropdown should be populated
Screenshots
Please complete the following information: (*)
The text was updated successfully, but these errors were encountered: