Manage separate Development, Staging, and Production environments directly from the Wordpress Admin screen.
PLX Multi-Environments manages separate Development, Staging, and Production environments directly from within the WordPress Admin screen.
Once the separate configuration files have been installed and your existing wp-config.php settings have been backed up
you\’re then free to enter each of your environments database settings. When you push your files between servers you no
longer need to edit the configuration.
Important: Although the plugin will automatically backup your current settings to wp-config.backup.php, we strongly recommend backing up
your wp-config.php file before completing the plugin installation.
/wp-content/plugins/plx-multienv
directory, or install the plugin through the WordPress plugins screen directly./wp-content/plugins/plx-multienv
directory, or install the plugin through the WordPress plugins screen directly.Yes, the plugin loads the relevant environment based on the current hostname so if you don\’t wish to use all the environments just leave those sections blank.
There are several ways you can do this:
* Add your code directly in the wp-config.php file, this file is created during the initial installation of the environments and can be safely edited without affecting the plugin, these settings apply globally to all environments.
* Un-install the plugin and directly edit each environment file (wp-config.development.php
, wp-config.staging.php
, wp-config.production.php
). Once the environment files have been created the plugin is only used to edit the files and is not needed for the environments to function correctly.
* Modify the template files found in /wp-content/plugins/plx-multienv/templates
, you will also need to edit the version number in /wp-content/plugins/plx-multienv/plx-multienv.php
to 999.9.9, this will prevent updates to the plugin that would otherwise overwrite your changes. Please note this method is not recommended as it disables future updates that may fix security vulnerabilities and provide compatibility with future versions of WordPress.