you should be able to use this hook which fires just before an auto update: do_action( ‘pre_auto_update’, $type, $item, $context ); $type can be ‘core’, ‘theme’, ‘plugin’, ‘translation’ a specific solution would depend on your particular backup plugin/service, but as long as this plugin/service provides either suitable hooks or an API it should be doable … Read more
On you future code files in your plugin, do not include the ‘option’ file in the repository. Since it is not included in the repository zip, the file (if it exists) will not be overwritten on the user’s system. You may need some code in your plugin to create the file on activation with some … Read more
It should last more than 15 minutes. See if there is .maintenance folder in WordPress installation folder or execute following command from wp-cli $ wp option delete core_updater.lock
This is a permissions (solved by chmod) issue. You don’t have enough privileges (755 at least) for WordPress to update. This also means you can’t write to wp-uploads and so on. Check this out: https://stackoverflow.com/questions/18352682/correct-file-permissions-for-wordpress
It is possible to filter the get_bloginfo(), but you’ll have to find a way to fine tune the conditional, because the override is global… add_filter( ‘pre_option_blogname’, ‘wpse_58030_override_blogname’ ); function wpse_58030_override_blogname( $bool ) { // If not page with ID == 28, do nothing if( !is_page( 28 ) ) return false; // Change the ‘blogname’ return … Read more
I don’t think its polite to send email to all users who Favorited your post. Because some people favorite your post to bookmark it. So don’t combine favorite with follow. So here is my suggestion: For bookmarking, use WP favorite posts plugin. As for the follow there is no plugin exists for normal wordpress installation. … Read more
Yes, the entire old directory will be deleted. So store files in the upload directory and other data in the database to keep all changes. From class Plugin_Upgrader: //Hooked to upgrade_clear_destination function delete_old_plugin($removed, $local_destination, $remote_destination, $plugin) { global $wp_filesystem; if ( is_wp_error($removed) ) return $removed; //Pass errors through. $plugin = isset($plugin[‘plugin’]) ? $plugin[‘plugin’] : ”; … Read more
Impossible. The path is hard coded in many places (wp-admin/includes/update-core.php for example). I think this is worth a Trac ticket, if there isn’t one already. We can move the directories for plugins, themes and mu-plugins. This is the last thing why we need a wp-content directory at all. Update There was a short discussion in … Read more
This issue is solved. The permission problem has to do with how files are uploaded to the WordPress site while updating. The suPHP solution is my preference at this point because it is simpler and requires less permissions on files, but if you don’t want to do that then you’ll have to take care to … Read more
Could not create directory is still a permissions error; have you checked Changing File Permissions « WordPress Codex? Are wp-content, themes and plugins 755? Any file that needs write access from WordPress should be owned or group-owned by the user account used by the WordPress (which may be different than the server account). For example, … Read more