Hot answers tagged

28

This is a read-write permission error. Fix this by changing the "wp-content" folder's permissions to 755. If this doesn't work checked the wp-config.php file and if it's not already defined, add define('WP_TEMP_DIR', ABSPATH . 'wp-content/');


22

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&...


20

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 sure if this is a ...


16

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 to. Ideally, you would store a “version” in your plugin’s database ...


12

It's impossible to help without having a look at your code. As I am one of the people who worked on WordPress 4.5.3, I can assure you that it's a usual maintenance and security release. There were no database-related changes between these versions except for #36748. Citing the commit message here: Database: dbDelta() will no longer try to downgrade the ...


12

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 ( file_exists( $theme ...


9

Each of the files you have mentioned are theme files. When you upgrade WordPress itself, it will not touch any themes (or plugins) you have installed, whether or not you have modified them. If this was a theme you created yourself, then you have no worries at all. However, if this was a theme created by someone else, for example a WordPress default theme, ...


8

I use XAMPP myself, but WAMP isn't much different. I'll bet you have not enabled the curl module. WordPress can use other methods (streams and fsockopen) as a fallback, but these may be disabled by default as well in a stock install. Curl is preferred and easy to enable. Close WAMP Go your the \bin\php\version directory in WAMP Edit the php.ini, and ...


7

The other way is to have people add their own sub-plugin. For example, the code in your core plugin that gets the skins could be something like: function get_available_skins() { $skins[] = '/includes/default-skin.css'; $skins[] = '/includes/2012-skin.css'; return apply_filters( 'get_available_skins', $skins ); } Then, users can create a ...


7

I don't know if this will help or not, but worth a try. Create a Must Use plugin and drop this lines, see code comments: <?php /* Plugin Name: Network upgrade exception */ // Run only in the Upgrade screen add_action( 'load-upgrade.php', 'add_filter_wpse_115279' ); function add_filter_wpse_115279() { add_filter( 'http_request_args', '...


6

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', '&...


6

Try disabling your plugins directory. I've been fixing this repeatedly today. Disabling the plugin directory has, for me, allowed the page to load and complete the upgrade process. I suspect it is a specific plugin doing it but haven't determined which yet. Update If you have W3 Total Cache 9.5.1 installed, deactivate it and try again. That has been the ...


5

Cannot creating directories even through a 777 CHMOD imply that your FTP local users does basicaly not have the permission to write files on your machine, to fix that try to edit your vsftpd.conf file and check that write_enable is equal to YES Edit vsftp.conf file sudo vim /etc/vsftpd.conf then uncomment the existing line (or set it's value to YES) ...


5

The featured image itself-- the actual .jpg, or .png, most likely-- is saved to wp-content/uploads with primary image data saved to $wpdb->posts as an attachment post type. Additional relevant data for the image is saved in $wpdb->postmeta. What makes an image "featured" or not is an entry in $wpdb->postmeta under the key _thumbnail_id and a ...


5

You can remove you plugin from the updateble list with: add_action( 'plugins_loaded', function(){ add_filter( 'site_transient_update_plugins', function ( $value ) { if( isset( $value->response['google-analytics/google-analytics.php'] ) ) unset( $value->response['google-analytics/google-analytics.php'] ); return $...


4

Many plugins use /wp-content/custom-plugin-folder/ to store customized plugin data (WPTouch comes to mind). Just use the constants WP_CONTENT_URL and WP_CONTENT_DIR Docs to check for the existence of your folder and retrieve any available skins. The following article, although not directly related to this Question, explains the importance for plugins/...


4

Back up all your files and database And then install wp3.5 and activate each plugin one by one and see whether they are compaitable or not OR you can install a wp3.5 in any other subdomain(domain.yoursite.com) and then activate all those plugins and see if they are compaitable or not


4

It fails because there is already a theme with that name on the server. So the obvious solution is to remove the theme before you upload the new version. If you're wanting to use an update mechanism like the theme repo, but on a custom theme, there are udpater classes you can add, such as this one: https://github.com/UCF/Theme-Updater That particular one ...


4

Check file “/wp-includes/version.php” $wp_db_version = [some number value] against the database options table’s options_value. They should have the same number value. If those numbers are not the same, change the value in the options table to match the value in the version.php file.


4

When a major release is made, fixes are made to it, but it's rare that fixes to older versions are made. It has happened before, but it should never be relied upon, and there are a lot of bugfixes that are never backported. Sometimes a version will be tagged before a major release that isn't publicly announced, but these shouldn't be used if you have the ...


4

In a nutshell that should be considerably straightforward, WP just couldn't update itself in versions that far back. Codex has detailed instructions for upgrading from older versions, see Upgrading WordPress Extended. However overall it's usual for manual update - backup, replace core files, go through upgrade dialogs.


4

The virus part is going to be off-topic, but yes a fresh install is the way to go. What I would do to upgrade the site is: Backup everything-- PHP and database Install the old site on a development server. Before running the site, replace all of the core files with new 2.8 ones from the archive. This will hopefully fix the suspected virus problem. Then ...


4

I had that on one of my sites recently (set to auto update core, so not sure if on 3.9 or one of 3.8.*). Flushing cache fixed it — wp cache flush via wp-cli, I imagine other ways would work just as well.


4

Since WordPress 3.9 you can use upgrader_process_complete hook. See reference 1, 2 Here is an example code: <?php /** * Plugin Name: Test plugin 1 * Plugin URI: http://rundiz.com * Description: A very simple plugin for testing. This plugin do nothing. * Version: 0.1.8 * Author: Vee Winch * Author URI: http://rundiz.com * License: MIT * License ...


4

In short, no. But it's not particularly complicated. Just add a new version_compare block each time you revise the database: $db_version = get_option( 'my_plugin_version' ); if ( version_compare( $db_version, '1.1', '<' ) ) { // Initial update code added in 1.1 } if ( version_compare( $db_version, '1.2', '<' ) ) { // Additional update code ...


4

4.0 made a change to the structure of the authentication cookie and added a "token" feild to it. I assume that you were logged out because your older style cookie didn't match the new format.


4

WordPress 4.0 is not a major update, at least referencing the scheme {major}.{minor}.{patch}. However, WordPress version numbering is explained here, and major versions are identified by the first two numbers, e.g. some recent major versions were 3.7, 3.8, 3.9, 4.0, and 4.1 coming in December 2014. WordPress noted in the release post, "4.0 is just another ...


4

I had to also change the owner of the root web directory. chown apache:apache . # or chown apache:apache /var/www/html Edit by Otto: Chloe, as you asked for more information than I could reasonably put into a comment, I'm appending this on to your answer. I hope that is okay. If not, feel free to revert it, or let me know and I will do so. The reason ...


4

I have about 20 sites to update to 4.7. Those without W3 Total Cache or with this deactivated previously are upgrading fine. Those with are problems. Also I have just gone in to deactivate W3 Total Cache on one and immediately went into error condition at the backend - frontend ok. The solution that works is : Rename wp-contents/db.php, say by appending ....


3

turned out to be a disk space error for me. I deleted a few backup files and I no longer had a permissions issue.


Only top voted, non community-wiki answers of a minimum length are eligible