WordPress Manual Upgrade for Experts: Difference between revisions
m Root moved page WordPress Manual Upgrade for Administrators to WordPress Manual Upgrade for Experts without leaving a redirect |
mNo edit summary |
||
| Line 46: | Line 46: | ||
*Make sure the wp-config.php file is in the upgrade directory (The "original / working" version of the file should be copied with the above CP command as it does not typically exist in a newly extracted version of WordPress (it's generated)) | *Make sure the wp-config.php file is in the upgrade directory (The "original / working" version of the file should be copied with the above CP command as it does not typically exist in a newly extracted version of WordPress (it's generated)) | ||
*Also remember a LOT of extensions make use of an .htaccess file (with Apache and other web servers) to modify the behavior of a WordPress site, so make sure that file from the original version of that file is copied into the upgrade directory (its a hidden file, so make sure). | *Also remember a LOT of extensions make use of an .htaccess file (with Apache and other web servers) to modify the behavior of a WordPress site, so make sure that file from the original version of that file is copied into the upgrade directory (its a hidden file, so make sure). | ||
=== Plugins === | |||
My strategy on upgrading plugins is to make a manual copy of their physical directory (see command below), then use the GUI to upgrade the plugin. If everything works, great, if not, go back to the original version<syntaxhighlight lang="text"> | |||
cp -ax WhatEverExtension WhatEverExtension.BackUp | |||
</syntaxhighlight> | |||
==Final Thoughts== | ==Final Thoughts== | ||