The error isn’t actually caused by your PHP version (PHP 4 constructors won’t be removed until PHP 7) – it’s a warning produced by WordPress in preparation for this. Each repetition of the error represents a plugin using the outdated code. Until your plugins’ authors update them, you can run the following shell command on … Read more
First of all… It is a really bad idea to modify existing plugin. But if you really have to do this, then you can hide update link with this code (this one works for Yoast SEO): function remove_update_notification_link($value) { if ( array_key_exists(‘wordpress-seo/wp-seo.php’, $value->response) ) { $value->response[ ‘wordpress-seo/wp-seo.php’ ]->package=””; } return $value; } add_filter(‘site_transient_update_plugins’, ‘remove_update_notification_link’); The … Read more
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.
I ended up using code from this post on WordPress.org Place this into my wp-config.php file if(is_admin()) { add_filter(‘filesystem_method’, create_function(‘$a’, ‘return “direct”;’ )); define( ‘FS_CHMOD_DIR’, 0751 ); }
Update & the internal WP HTTP API A slightly modified version of my answer to this question, but also as a plugin that shows how it could work. Note: The code is not tested – I don’t know your server setup, etc. – and just written out of my head. You’ll have to test it, … Read more
Not sure if there actually is a in scope answer for what you are asking, but the below are some hopefully helpful informations/thoughts. Besides that, I don’t know about (all) the tools you are mentioning, but thats secondary anyway. What you want, of course, is to keep the development process, like you described it, alive. … Read more
Skimming through the Core_Upgrader::should_update_to_version() method, it looks like we can override the defined( ‘WP_AUTO_UPDATE_CORE’ ) // true (all), false, minor check, used to setup the local boolean variables$upgrade_dev, $upgrade_minor and $upgrade_major, with the following filters: … apply_filters( ‘allow_dev_auto_core_updates’, $upgrade_dev ) … apply_filters( ‘allow_minor_auto_core_updates’, $upgrade_minor ) … apply_filters( ‘allow_major_auto_core_updates’, $upgrade_major ) … So these filters have … Read more
Try This First: Your Problem Might Be DNS In my testing this is a problem with DNS resolving. In my case it’s because the DNS filter/cache I run on my local network wasn’t responding to requests. After restarting the service on the DNS server my requests got through quickly & easily. I would suggest checking … Read more
Hooks The hooks you’re searching for are ‘pre_set_site_transient_update_plugins’ and ‘upgrader_post_install’ The later takes three arguments. Example: function upgrader_post_install_cb( $true, $hook_extra, $result ) and should be used for: Move & activate the plugin, echo the update message. Moving plugins Moving works like this: $wp_filesystem->move( $result[‘destination’] ,’your_destination_path’ ); Then use activate_plugin( ‘path/file’ ); after moving.
You actually have several questions in there, so I’ll answer them one by one: However, if I simply do this on my main plugin file, it doesn’t work: add_filter(‘pre_set_site_transient_update_plugins’, array(‘XYZ’, ‘check_update’)); First of all, I’d like to understand what’s the difference between the two scenarios. This is failing because you are calling the method statically, … Read more