Hooks to run after a core upgrade?
Check the filter update_feedback, he works after the update and you can use for all stuff after an update. An example plugin can you find in this trunk.
Check the filter update_feedback, he works after the update and you can use for all stuff after an update. An example plugin can you find in this trunk.
I’ve finally found the answer. Yes WP was ‘triggered’ to think it was evaluating a WordPress and not a WordPress-MU table structure. This was caused by the following lines: define(‘WP_ALLOW_MULTISITE’, true); define( ‘MULTISITE’, true ); in the wp-config.php that should NOT be there in a WordPress-MU 2.9.2 installation (but that some former developer had tossed … Read more
Try working through the solutions listed in: Troubleshooting WordPress 3.3 – Master List
I’ve never had any luck with dbdelta, it has worked spottily at best, and when I code, that’s just not good enough. My method for handling DB changes is to use database versions. So when I create a plugin, I also set the database version, then if I want to update the database, I do … Read more
Quick and easy. if ( is_plugin_active( ‘plugin-folder-name/main-plugin-file.php’ ) ) deactivate_plugins( ‘/plugin-folder-name/main-plugin-file.php’ ); It’s important to note the is_plugin_active string is slightly different than the deactivate_plugins string.
Never try to upgrade that many versions in a single step! You will need to carry out a series of smaller, manual, upgrades: 2.7 -> 2.8 -> 2.9 -> 3.0 -> 3.2 -> 3.3.1 ->3.3 I would deactivate all plugins and switch to default theme when you get to current version, switch themes to what … Read more
wp-content should be 755, otherwise WordPress will think it has global write access, and won’t fallback to the FTP filesystem method if it doesn’t. Might be worth checking if PHP is running in safe mode – this can also be the troublemaker (though I’m aware WordPress can still upgrade with it on).
The debug mode is on on your site. Go into wp-config.php and look for: define( ‘WP_DEBUG’, TRUE ); Change TRUE to FALSE. See Debugging in WordPress for more information. If this doesn’t help the error_reporting level is set somewhere else. .htaccess: Look for … php_value error_reporting integer … where integer matches one of the error … Read more
Okay I found the issue. It was a problem with my “Nexus” theme. For anyone with the same issue, I commented out the line “wp_enqueue_script(‘jquery-prime-options’…” in this function : “option_tree_load”
Unfortunately, it looks like the WordPress update failed. The good news is that it’s an easy fix. Simply download the files and re-upload them. You can follow the instructions here: http://codex.wordpress.org/Updating_WordPress#Manual_Update