wp-config.php wth Auto Upgrade

I dont think it does any modification to the configuration file during an upgrade. I have a site for many years and it was “auto upgraded” a few times and wp-config is exactly the same.

If you think, theres no need to change the data there, unless of course you change your database connection info so theres no reason why wordpress should edit that file ??

I just stepped through a series of upgrades manually as follows: 2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.1

As I stepped through, expansion to the wp-config.php file occurred. Examples:

• define(‘DB_CHARSET’, ‘utf8’);
• define(‘DB_COLLATE’, ”);
• define(‘AUTH_KEY’, ”);
• define(‘SECURE_AUTH_KEY’, ”);
• define(‘LOGGED_IN_KEY’, ”);
• define(‘NONCE_KEY’, ”);
• define(‘AUTH_SALT’, ”);
• define(‘SECURE_AUTH_SALT’, ”);
• define(‘LOGGED_IN_SALT’, ”);
• define(‘NONCE_SALT’, ”);

It piqued my curiosity as to whether or not the Auto (ftp) update/upgrade function would have been intelligent enough to make the appropriate updates to the wp-config.php file.

Yes as you went through the steps all files and folders got updated as well as there are lots changes made to core files since 2.1

Well its easy … just download the latest version and check the wp-config-sample file. Then compare with your auto modified version to see if you have any unnecessary code on yours.
Then you will see if the upgrade function was intelligent enough or not ??

No kidding guys…really ? I know what needs to be done.

The original question is “How does WP handle structural changes to the wp-config.php file when I do an Auto Upgrade.”

The answer is “it doesn’t”. Therefore,

WordPress does not alter your wp-config.php with any enhancements that may come out of the new release. You must manually compare your config file to the new sample config.

And I am fine with that procedure. Just wanted to know how WP handled it.

Thanks for the feedback.

You don’t HAVE to manually check the config file. I’ve done lots of auto upgrades on my sites and never verified the file afterwards. it just works fine :p

So when you went from the version that did not have the AUTH_KEY constant defines to the versions that used them, how did you account for those defines in your config file?

I didn’t.
Thats an optional function its not mandatory ..
The authentication keys are meant to increase security on your passwords, but your site can work fine without it.

But with all due respect, you continue to miss the point.

Yeah i know …
but you already answered your question on the post above ??