I seem to remember running into this myself when i tried it months ago, also on Valet but i dont think that was the problem. i did solve it but i cant remember how. All i can suggest is trying the version of the starterkit made by the same people that includes Blade, and compare to see if you have set it up properly.
I was using the blade plugin by @beebmx. This worked fine an then I updated to the new on. Since then, the problem started.
Now I downloaded a fresh starterkit added the blade plugin via composer:
composer require afbora/kirby-blade
… and got the same error.
the beebmx/kirby-starterkit is working with Kirby-env an I dont wanted to work with a build process or seperated src and public folder. But there is no illuminate Folder and no conflict so.
- Installing illuminate/support (v5.8.27): Loading from cache
is any of them required:
illuminate/support suggests installing moontoast/math (Required to use ordered UUIDs (^1.1).)
illuminate/support suggests installing ramsey/uuid (Required to use Str::uuid() (^3.7).)
illuminate/support suggests installing symfony/process (Required to use the composer class (^4.2).)
illuminate/support suggests installing symfony/var-dumper (Required to use the dd function (^4.2).)
illuminate/support suggests installing vlucas/phpdotenv (Required to use the env helper (^3.3).)
Now I realize why the error was caused. It loads the Laravel library on your system before the Kirby application. Kirby core files need to be loaded first for blade plugin work stable.
I guess you load the kirby and kirby-blade repository from root composer. Try to install blade plugin from /site/plugins folder.
Thanks @ahmetbora,
that did the trick. It was’nt clear to me that I should have to install a own composer for plugins.
I hope I didn’t waste your Time,
thanks again @TakioTk
Any other way than a second composer json in plugins folder? I mean, that makes a composer based worklfow a little bit obsolet But I can’t figure out how to tell Kirby to run core first before the View lib…
Just for information if anybody is interested: if you use it as a git submodule or download it directly, the plugin works fine.
Would could be the reason it doesn’t work with composer? I’m not an composer expert