Studio: Add config constants to mu-plugins #766
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issues
Closes https://github.com/Automattic/dotcom-forge/issues/10148
Proposed Changes
This PR adds polyfill to
mu-plugins
for database constants in case they are not defined in thewp-config.php
file when it is being imported. This ensures that the database constants are defined at all times.Testing Instructions
wp-admin/plugins.php?plugin_status=mustuse
and confirm that the0-wp-config-constants-polyfill.php
plugin is present thereAlternatively, you can export a Studio site, edit
wp-config.php
file and remove the constants such asDB_HOST
etc. from that file. You can then attempt to import it and confirm that the import succeeds and that the site starts successfully.Pre-merge Checklist