You can Disable HTTP Calls by adding this in your wp-config.php define( ‘WP_HTTP_BLOCK_EXTERNAL’, TRUE ); This will disable/block all external HTTP requests and will make website alot faster. And then you can whitelist domains that you don’t want to block. define( ‘WP_ACCESSIBLE_HOSTS’, ‘example.com, domain.com’ );
It should be relatively safe to chmod it to 777 for as long as you need to in order to upgrade, and then change back to what it was before. Generally speaking, 755 is the recommended directory permission.
As so often, WP-CLI already has you covered: wp core update –version=3.8 ../latest.zip Have a look here for more details: http://wp-cli.org/commands/core/update/
How to disable core auto updates but enable plugins and themes auto updates If you want to stop the autoupdates of the WordPress core, but to enable them for your Plugins and/or Themes, you can add these lines in the wp-config.php file: Stop the core auto updates: define( ‘WP_AUTO_UPDATE_CORE’, false ); Then Enable the plugins/themes: … Read more
I’m not aware of any solutions for iterating through and automatically updating your list of plug-ins, but my guess is that any system that can automatically update WordPress itself can be modified to update everything in fairly short order. That said, I know of two good ways to update WordPress automatically: WP Remote This is … Read more
You can hook on option_update_core and edit the update url, as a plugin you can do something like this (Remember to disable the plugin after updating wordpress) add_filter(‘option_update_core’,’wpse_26750′); add_filter(‘transient_update_core’,’wpse_26750′); function wpse_26750($options){ global $wp_version; $updates=array( ‘2.5’=>’http://wordpress.org/wordpress-2.5.zip’, ‘2.7.1’=>’http://wordpress.org/wordpress-2.7.1.zip’, ‘2.8’=>’http://wordpress.org/wordpress-2.8.zip’, ‘2.8.1’=>’http://wordpress.org/wordpress-2.8.1.zip’, ‘2.8.3’=>’http://wordpress.org/wordpress-2.8.3.zip’, ); $currentUpdate=$options->updates[0]; //Add Previous updates skipping the ones already passed foreach($updates as $version=>$updateUrl){ if( version_compare($wp_version,$version) < … Read more
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.
I’m not sure if this will address your issue… But there’s something new in WorldWordPress. http://infinitewp.com/ It’s akin to ManageWP, but free :o) I’m not affiliated with them in any form, just starting to play with it. (ht: wpmail.me) It’s a platform that you install in your server. Add the client plugin to your WPs. … Read more
quick-and-dirty hint to solve this problem: find the function list_translation_updates() in wp-admin/update-core.php $updates = wp_get_translation_updates(); if ( ! $updates ) <- locate the if … } else { <- add this print_r ( $updates ); } add the else-case and save the file reload the dashboard page and you will get the desired information.
The issue is, there is no value for local_package in the URL. At first I thought this might be a bug. Similar issues have been reported before (see here and here. I then stumbled on comment in trac ticket 8729 where user nbachiyski explains how localization should work: There are two ways to localize WordPress: … Read more