Closed roborourke closed 4 years ago
Realised this might well be because I have a WP_INSTALLING
check on the project I noticed this on which means the cavalcade plugin isn't loaded during install.
The problem is that this installs the cron runner, but not the WP plugin. Once you install the WP plugin via composer and activate it, then restart the service it runs as expected.
@svandragt good catch! Interesting then, there are a good few methods the plugin might be included / activated by. I'm not sure we'd want the extension to install the plugin as it's something the project should include, or at least is in the case of HM projects.
Yeah I agree that the extension shouldn't install the plugin as you might want to use it as a plugin, mu-plugin or even autoloaded so I'm going to close this out.
What operating system do you use? OSX
What version of Vagrant are you running? 2.1.2
Are you using VirtualBox or VMWare and which version are you using? Virtualbox 5.2.16
Do you have a custom YAML file? If so, what does it contain?
The problem is that the database (even if created) does not contain the cavalcade tables until the site has been visited. The db table creation logic is contained in the plugin rather than the runner, the end result is that on a clean provision when trying to bring up the cavalcade service it fails because those tables are missing. A second provision after visiting the website or running it via a WP CLI command is required to activate the service.