WordPress Manual Upgrade for Experts: Difference between revisions

Line 44:

Flags can be combined, IE -Rnvax, but are shown separately for clarity.

</syntaxhighlight>

*Make sure the wp-config.php file is in the upgrade directory (~~there shouldn't be a wp-config.php~~ file ~~in the upgrade folder and it~~ should be copied with the above CP command)

*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 use ~~the~~ .htaccess file to modify the behavior of WordPress, so make sure that file from the original version of that file 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).

== Final Thoughts ==

Depending on the complexity and customization of the WordPress Site, there may be complications. For me, there were two plugins that didn't function at 100%. You'll probably have some issues too. The first best solution after upgrading WordPress is to update extensions too. Make a copy of your upgraded WordPress site in case any extension upgrades mess things up.

=== Magic Zoom ===

A great plugin that I really like, called Magic Zoom, which provides a zoom window like a magnifying glass to enlarge images had an 'image cache issue' that I was able to fix with a CHOWN command.

=== Image Map Pro ===

Image Map Pro, a plugin that allows custom regions to be defined on an image that produce a popup word balloon also wasn't functioning. After some quick troubleshooting I determined it was related to images that had been uploaded before the site had been converted to use HTTPS. The fix was fairly simple: Re-select the same image while connected via HTTPS.

@@ Line 44: / Line 44: @@
 Flags can be combined, IE -Rnvax, but are shown separately for clarity.
 </syntaxhighlight>
-*Make sure the wp-config.php file is in the upgrade directory (there shouldn't be a wp-config.php file in the upgrade folder and it should be copied with the above CP command)
+*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 use the .htaccess file to modify the behavior of WordPress, so make sure that file from the original version of that file 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).
+== Final Thoughts ==
+Depending on the complexity and customization of the WordPress Site, there may be complications.  For me, there were two plugins that didn't function at 100%.  You'll probably have some issues too.  The first best solution after upgrading WordPress is to update extensions too.  Make a copy of your upgraded WordPress site in case any extension upgrades mess things up.
+=== Magic Zoom ===
+A great plugin that I really like, called Magic Zoom, which provides a zoom window like a magnifying glass to enlarge images had an 'image cache issue' that I was able to fix with a CHOWN command.
+=== Image Map Pro ===
+Image Map Pro, a plugin that allows custom regions to be defined on an image that produce a popup word balloon also wasn't functioning.  After some quick troubleshooting I determined it was related to images that had been uploaded before the site had been converted to use HTTPS.  The fix was fairly simple: Re-select the same image while connected via HTTPS.