There are no errors on deployment. However my client requires the integration of Veeqo, a stock management software, that has an integration plugin for wordpress.
In the instructions here, I’ve completed both steps 9a and 9b.
Which state that I upload to the wordpress root, a folder, and set its permissions to 755 and 644 on the files it contains. But the above error is still present.
A test was done on a traditional server stack (one click install), which worked.
I’m guessing the error above is because bedrock’s file structure is different to a traditional wordpress architectur, and the bridge file is pointing to an incorrect directory.
The documentation at that link says you need 9a or 9b, not both. What happens if you only install the plug-in (and don’t have the “bridge file” stuff added via FTP). Do you get the same error?
Bedrock does use a specialized directory layout, but it conforms to everything WordPress requires and supports. Plugins that don’t work with it are generally at fault. See: https://roots.io/bedrock/docs/bedrock-compatibility/
It does sound likes it’s having trouble connecting to your DB, but the include line you mention doesn’t sound like it’s trying to load a WordPress file: WP’s include folder is wp-includes, and the WP DB config isn’t I’m there anyway.
It doesn’t need to reference the vault file: the vault is only for Ansible when it deploys. Once deployed Bedrock uses the .env file generated by Ansible on the remote server to get things like DB connection credentials. It makes those available as constants for scripts loaded afterward (i.e. wp-config.php).
Without seeing the bridge script it’s hard to guess where the problem is. If Veeqo is a paid product they should offer support, so you should contact them.
I’ve been on IM for hours with their support, who’ve asked about adding the file to the nginx config.
The nginx error log on the DO droplet is empty tho.
How would I even go about adding it to the config? Is that a vagrant thing or Ansible also?
Once again, thank you for your support. It’s why I chose to use Roots in the first place.
Have you tried the plug-in version if the bridge by itself? If it’s loaded as a plug-in it should have access to all of WP’s internals and would need to be making this guesses about where things are in the filesystem.
Yes first try was with the plugin, and now I’ve done it by the deploy script, as in its on the repo. And made sure the permissions are correct.
Still no joy.
That kind of depends on the specific request and how your server is configured. I’m not sure what whitelisting an IP would have to do with your problem, but that would probably be done either at the server level through whoever your host is, or by editing some server config files at a lower level (i.e. .htaccess if you’re on Apache).
@ShaunMac what mysql version are you running? mysql --version
if it’s 8.0.16, I think I know what might be going on…
something about php/mysqli does not natively support an updated authentication strategy… I ran into similar issue with a new local install of WP… This fixed it for me: ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '{yourPW}';