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
Just fixed up that missing Craft reference. And it depends on how your module is setup, there's lots of bootstrapping to do to get various things working like controllers which is why it might be useful to extend our base module as a starting point. Or, you can copy-paste from the previous link.
I change the module to use Craft::setAlias('@modules/vizymodule', __DIR__); and in the Asset Bundle class to use $this->sourcePath = '@modules/vizymodule/assets'; and this seems to have cleared up the error running console comands.
Question
We've followed the documentation on https://verbb.io/craft-plugins/vizy/user-guides/creating-a-custom-node-from-scratch to create a new module.
We had to add
use Craft;
to fix theClass "modules\vizymodule\Craft" not found
error thrown by the lineCraft::setAlias('@vizy-module', __DIR__);
The pulgin works as expected until we try and run any craft command line commands, then we get the error:
Any ideas how to get around this?
I've tried adding a default controller in
/controllers/DefaultController.php
but this doesn't fix the issue.Additional context
Craft edition & version | Craft Pro 4.5.9
Vizy | 2.1.12
The text was updated successfully, but these errors were encountered: