-
Notifications
You must be signed in to change notification settings - Fork 26
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
Issues with Wordplate #33
Comments
I always wanted to test WordPlate - now I'll have some extra motivation. I
hope I'll be able to do this during the weekend
śr., 23 wrz 2020, 12:41 użytkownik antoineLZCH <[email protected]>
napisał:
… Hi,
I just found your package which could help me a lot to build blocks with
Timber.
I am using Wordplate <https://github.com/wordplate/wordplate#readme>
which is probably something similar to Bedrocks, but the truth is it
doesn't detect any of my created blocks (I stored these in
theme/${themeName}/views/blocks, not in
themes/${themeName}/theme/views/blocks). Maybe I don't do it well ?
I tried to install the package on Wordplate's composer without any good
result and I saw someone had the issue installing the package with
Bedrocks' composer, so I tried, as you mentioned, to install it directly in
the timber theme directory (I used this one
<https://github.com/timber/starter-theme/tree/2.x> as a replacement for
my usual wordplate boilerplate theme), which causes the same issue than
before : My blocks are not recognized aswell.
You mentioned that you were creating a plugin version of the package, do
you have any informations about this ? Or instead, could you please help me
solving this issue ?
Thanks in advance !
Best regards,
Antoine
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR34OVY3FIFDL3GQI5MJE3SHHGGFANCNFSM4RW32PXA>
.
|
Wordplate is really nice. I don't think there's so much differences between it and Bedrocks. |
Sorry it took so much time - I was able to test it and I see everything is working fine, although I made one mistake and you probably did too :) First of all check the main composer.json file - if there is Next go to theme folder and check if there is Overall be sure that library is only installed in the theme :) |
Same problem here with timber-starter-theme v2.0 (as mentioned above by antoineLZCH). I get a fatal error: In v2.0 of the theme there's a new folder structure, so the recognized theme folder is /themes/[my-theme]/theme/ So I think that's why there's no directory name. Similar problem here: timber/starter-theme#105 |
Hello, sorry I just saw your answer. @Zielgestalt We used the timber starter theme 2.0 aswell at work, if you have any solution, it's fine for us. For now, we just created our blocks handmade. I'll try to think about a solution later ! |
@antoineLZCH from what I heard this library should work as a plugin with just some minor changes. Maybe it's time to finally create it. I just have to think of a way how to automate this. |
I had some issues with bedrock, so within my theme
Now my blocks are showing |
Hi,
I just found your package which could help me a lot to build blocks with Timber.
I am using Wordplate which is probably something similar to Bedrocks, but the truth is it doesn't detect any of my created blocks (I stored these in theme/${themeName}/views/blocks, not in themes/${themeName}/theme/views/blocks). Maybe I don't do it well ?
I tried to install the package on Wordplate's composer without any good result and I saw someone had the issue installing the package with Bedrocks' composer, so I tried, as you mentioned, to install it directly in the timber theme directory (I used this one as a replacement for my usual wordplate boilerplate theme), which causes the same issue than before : My blocks are not recognized aswell.
You mentioned that you were creating a plugin version of the package, do you have any informations about this ? Or instead, could you please help me solving this issue ?
Thanks in advance !
Best regards,
Antoine
The text was updated successfully, but these errors were encountered: