Since Changeset 44524, which has landed in WordPress 5.1, the variable $theme is now a global variable set by WordPress which also gets unset after the themes have been bootstrapped: // Load the functions for the active theme, for both parent and child theme if applicable. foreach ( wp_get_active_and_valid_themes() as $theme ) { if ( … Read more
You need to run the chown command on whole wp-content directory: chown www-data:www-data /path/to/wp-content/ -R
I’ve did a quick test on just changing the option and it seems to work. What I did is: Wrote a widget that has just 2 fields: “Title” and “Name”. Add several instances of this widget to my sidebars. Been sure that they are shown correctly in frontend. Edited the class to use 3 fields: … Read more
Don’t remove the action but add your own before it. If you remove the action you will never get the message saying it was upgraded successfully. Here you can provide your own info on what to do next. function tp_dont_redirect_to_about_wordpress( $new_version ) { global $wp_version, $pagenow, $action; if ( version_compare( $wp_version, ‘3.4-RC1’, ‘>=’ ) ) … Read more
Configuration instructions in Codex on Enabling SSH Upgrade Access recommend either: Using SSH SFTP Updater Support plugin from official repository. Using built–in SSH2 support, which requires the PECL SSH2 extension installed on the server. It used to refer to this tutorial: Using SSH to Install/Upgrade in before, which might be of use.
W3-Total Cache has a feature that will scan all your posts and import any external images into the media library and change the paths to the new location. See Screenshot
I had the same problem recently. For some reason the option db_upgraded isn’t set by the upgrade process. Fix Go to /wp-admin/options.php. Fill the field db_upgraded with a 0 (zero). Hit Save Changes. Done.
The problem, it turns out, was that the db_version field in the wp_options table and the wp_db_version variable in the file /wp-includes/version.php didn’t match. In my case (an upgrade to 3.5.2) the database showed “22441” while the PHP file showed “22442”. Changing the number in the database to “22442” solved the issue. I’m not quite … Read more
Using WP-CLI you can specify this as described in the official documentation. $ wp plugin update <plugin> Using either of the following arguments –minor Only perform updates for minor releases (e.g. from 1.3 to 1.4 instead of 2.0) –patch Only perform updates for patch releases (e.g. from 1.3 to 1.3.3 instead of 1.4) –version=<version> If … Read more
I don’t think an action has been added. You can look at version details for any version and see any new actions added. The WordPress Way to run code on plugin update is what is described here: The proper way to handle an upgrade path is to only run an upgrade procedure when you need … Read more