I found the answer here: If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled. (I found this answer which will tell you how to avoid using FTP.) If the install is running as a SVN or GIT checkout, automatic updates are disabled If the constants DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED are … Read more
For regular users, the preferred update method is pressing the “Update” button in wp-admin. For sysadmins, wp core update + wp core update-db will probably be a lot faster. Note that for multisite instances, you’ll have to update the DB for each site in the network. See https://github.com/wp-cli/wp-cli/issues/683 NB: I might be biased, since I’m … Read more
When on the admin view you can use the following functions to get update data. get_plugin_updates() get_theme_updates() get_core_updates() If you want to build your own functions, then you can get update related data from site transients update_themes, update_plugins, and update_core. Then you can compare the plugin and theme transients with the theme and plugin arrays … Read more
register_activation_hook() is only called when the user activates the plugin. It is not called after a plugin upgrade. The preferred method of handling upgrades is using register_activation_hook() to store the current version in the wp_options table and then checking it on each admin page load.
what about something like this on activation? function wpa47153_run_once(){ $posts = get_posts(array(‘numberposts’ => -1) ); foreach($posts as $p) : $meta = get_post_meta($p->ID, ‘meta_key’,true); if($meta) : $my_post = array(); $my_post[‘ID’] = $p->ID; $my_post[‘post_content’] = $meta . “<br/>” . $p->post_content ; // Update the post into the database wp_update_post( $my_post ); unset($my_post); //remove the meta key delete_post_meta($p->ID, … Read more
Yep Its possible if you hook a function to site_transient_update_plugins filter hook and check if plugin is activated using is_plugin_active like this: add_filter(‘site_transient_update_plugins’, ‘remove_update_nag_for_deactivated’); function remove_update_nag_for_deactivated($value) { foreach($value->response as $key => $val){ if (!is_plugin_active($val)) unset($value->response[ $key]); } return $value; }
Don’t modify core, use the actions and hooks system instead add_action( ‘login_init’, ‘yourloginoverrides’ ); function yourloginoverrides() { // do some check and call wp_redirect if its true or whatever you wanted to do }
Any database changes WP itself needs are performed automatically. On first load after core update you will get (if required) special page that will say that database update is required and perform that update. No actions required from you really. Changes and updates to database by plugins can vary and not many plugins actually need … Read more
Maybe upgrader_process_complete() action hook. Fires when the bulk upgrader process is complete. On line 761 of wp-admin/includes/class-wp-upgrader.php From source: /** * Fires when the upgrader process is complete. * * See also {@see ‘upgrader_package_options’}. * * @since 3.6.0 * @since 3.7.0 Added to WP_Upgrader::run(). * @since 4.6.0 `$translations` was added as a possible argument to … Read more
If possible, you should try and fix the cause of this error – invalid SSL certificates. But there are some instances where this is not possible or desirable. One obvious one being development sites using a self-signed SSL certs. One way around this is to set $ssl_verify to false before line 1161 of wp-includes/class-http.php: curl_setopt( … Read more