WP.pro automatically reviews the wp-config.php file after each modification, making necessary corrections or additions as needed. This helps prevent configuration errors and simplifies the setup and maintenance process for our customers.
Automatic adjustments ensure that the configuration file is always accurate and complete, ensuring a smooth installation and operation of WordPress on the WP.pro Hosting Platform.
When modifications are made to the wp-config.php file, the PHP OpCode and other relevant caches are automatically flushed. This ensures that changes take effect immediately.
Constants Automatically Adjusted by WP.pro
DB_NAME
We automatically update the DB_NAME constant to ensure the correct database is always referenced in the configuration, preventing potential connection issues.
DB_USER
The actual username required for authentication with the MySQL database. The DB_USER constant will be automatically updated, if necessary.
DB_PASSWORD
No matter if you are creating a new WordPress site, updating a version, or changing the password through the WP.pro API or UI, our automation ensures that the password in your wp-config.php is updated as quickly as possible.
DB_HOST
We automatically set the value for `DB_HOST` to 127.0.0.1 because this routes your connection and SQL queries efficiently and ensures they are processed as quickly as possible. Learn more about the MySQL infrastructure and why, with WP.pro, you always connect to your MySQL database using 127.0.0.1.
DISABLE_WP_CRON
The automatic correction to the value “false” might initially seem unusual or even confusing, as you want important jobs in WordPress to be executed. The reason for disabling (or WP.pro-specific redesign) lies in the fact that WordPress is designed to check and execute crons on every single page load. This can cause latency and load, which can be avoided with a properly designed architecture like WP.pro.
In WP.pro hosting, the WordPress cron is executed automatically in the background at regular intervals, so it doesn’t need to be triggered on each page load. This approach optimizes performance and reduces unnecessary load.