You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having an issue using sage-directives after upgrading to Acorn v3. I can use directives within blade files as per usual and everything works correctly when viewing the site but I can no longert use wp cli.
Upgrade Acorn from version ^2.1 to version 3.0
Run wp acorn
The cli doesn't return any output and the following error is added to the debug.log:
I wonder if there's any reason for sage-directives to be included in wp cli. For now, I excluded the library from wp-cli by checking if blade.compiler exists too.
if (function_exists('Roots\app') && \Roots\app()->bound('blade.compiler')) {
return\Roots\app('blade.compiler');
}
I can confirm the same behavior as @mrmadhat in a clean install of Sage 10 with Acorn v3.0 and that @iniznet's edit to sage-directives/src/Directives.php allows wp-cli to function again.
I'm having an issue using sage-directives after upgrading to Acorn v3. I can use directives within blade files as per usual and everything works correctly when viewing the site but I can no longert use wp cli.
^2.1
to version3.0
wp acorn
The text was updated successfully, but these errors were encountered: