-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Dockware contribution not working as expected #32
Comments
Now I made a complete new container with dockware/dev (knowing /platform and psh.phar is missing). tabs.html.twig is still not read in, although it's there: Sure, I cleared cache (bin/console cache:clear) ;o) Please help. |
I'd like to push that issue, because no dev possible :o( |
can you upload your plugin here? |
Here we are. |
cheers ps. this has nothing todo with dockware, this is basic shopware 6 way how themes are working. |
Oh, then I must apologize if that was on me....! I didn't find this hint in the doc. Thanks a lot |
Nope, but if i do not i get a error with something like "base..." not found. |
great thanks for this outstanding support for a beginner !!! |
you are welcome! |
To my shame, I have to admit that I can't currently test it. I will test it this afternoon. Thanks again. If it does not work I would contact you again ;o) |
it works! Thanks |
I installed the dockware/dev successfully.
As I missed the psh.phar and linked platform folder, I switched to dockware/contribution.
Afterwards I made a Plugin and activated it - so far so good.
But TWIGs within my PlugIn are not read.
So I've searched for /config/packages/twig.yaml but it's not there?!
What is wrong with my environment and what's the difference between dockware/dev and dockware/contribution?
If I use dockware/dev then psh.phar and /platform is missing...
What I'm needing is just a full dev environment with all the tools, the correct template so I'd be able to develop a theme-plugin.
As for now (with dockware/contribution) my PgligIn is installed and activated but a html-twig is not used in my plugIn, although it's in the right place:
The text was updated successfully, but these errors were encountered: