The WordPress plugin provides some handy options to make setting up a
.probo.yaml file for your WordPress site easier. To use this plugin you must declare
plugin: WordPressApp in a step in your
WordPress core and plugins generally prefer absolute URLs for links and images instead of relative URLs. This means Probo needs to rewrite your data in order for links to work in the test environment. The
wpHome configuration options set the string values Probo will use to search for the appropriate base paths and replace them with the Probo environment’s URL.
The URL of the original site as stored in the database. This is replaced by the Probo URL in the database.
The homepage URL of the original site (including the domain). This is replaced by the Probo URL in the database.
The filename of the database to import if specified. Note that this database must be added to the Assets section separately.
The name of the database. Defaults to
Whether the database was sent gzipped and whether it should therefore be gunzipped before importing.
Database Collation Errors on Builds
Currenty in Wordpress 4.8.x+, the MySQL database collation can be in COLLATION format
utf8mb4_unicode_520_ci. This format is unsupported by our older Docker images depending on your site’s MySQL Server version. If you exported your database from MySQL 5.6 or higher, you might receive the following error when importing the DB to Probo:
ERROR 1273 (HY000) at line 25: Unknown collation: 'utf8mb4_unicode_520_ci'
Use one of our Ubuntu 16.04 or Ubuntu 18.04 Probo Docker images instead to resolve this issue as they have a newer version of MySQL installed supports
WP-CLI Version Errors
In some cases we have seen the wp-cli tool error out during a build using the
utf8mb4_unicode_ci DB collation. Updating the
wp-cli tool in the
.probo.yaml file resolves this issue. You will need to update your
wp-cli version if you receive the following error in your Probo build logs for the “Site setup” step:
Fatal error: Call to undefined function apply_filters() in /src/wp-includes/load.php on line 316
wp-cli in your
.probo.yaml steps, or use one of our Ubuntu 16.04 or Ubuntu 18.04 images to resolve this issue.
The directory of the actual web root. Defaults to
Whether or not to flush the cache. Defaults to
Whether or not to attempt to update any WordPress plugins to their latest versions. Defaults to
Using the Wordpress plugin