Se débarrasser de Une autre mise à jour est actuellement en cours

Il s'agit d'un verrouillage automatiquepourempêcher lesmises àjour simultanées du cœur.Il disparaîtra après 15minutes.Si vousne voulezpas attendre,supprimez l'enregistrement de latable d'options -généralement wp_options.

Depuis Wordpress 4.5:

 option_name = 'core_updater.lock'
 

Si vous avez uneinstallation plus ancienne (avant Wordpress 4.5):

 option_name = 'core_updater'   
 

It is an automatic lock to prevent simultaneous core updates. It will be gone after 15 minutes. If you don't want to wait, delete the record from options table – usually wp_options.

Since Wordpress 4.5:

option_name = 'core_updater.lock'

If you have an older installation (before Wordpress 4.5):

option_name = 'core_updater'   

Si vous utilisez wp-cli,exécutez la commande suivante:

 wp option delete core_updater.lock
 

Cette commande supprimera l'optionnommée: core_updater.lock

If you use wp-cli run the following command:

wp option delete core_updater.lock

This command will delete the option named: core_updater.lock

Ajoutez ce code àn'importe quelplugin ou aufichier functions.php de votrethème.N'oubliezpas de le supprimer lorsque vous avezterminépour éviter defeuilleter votrebase de données sans raison.

 delete_option( "core_updater.lock" );
 

Add this code to any plugin or your theme's functions.php file. Remember to remove it when you're done to prevent flicking your database for no reason.

delete_option( "core_updater.lock" );

Par @jeremyclarke,exécuter ceci sur leterminal a résolu ceproblèmepourmoi: wp option delete core_updater.lock

Per @jeremyclarke, running this at the terminal resolved this issue for me: wp option delete core_updater.lock

Confirmation de ce 'core_updater.lock'. Celapeutne pas être évident au début,mais regardez la ligne 771.

 File: wp-admin/includes/class-wp-upgrader.php
754:    /**
755:     * Creates a lock using WordPress options.
756:     *
757:     * @since 4.5.0
758:     * @access public
759:     * @static
760:     *
761:     * @param string $lock_name       The name of this unique lock.
762:     * @param int    $release_timeout Optional. The duration in seconds to respect an existing lock.
763:     *                                Default: 1 hour.
764:     * @return bool False if a lock couldn't be created or if the lock is no longer valid. True otherwise.
765:     */
766:    public static function create_lock( $lock_name, $release_timeout = null ) {
767:        global $wpdb;
768:        if ( ! $release_timeout ) {
769:            $release_timeout = HOUR_IN_SECONDS;
770:        }
771:        $lock_option = $lock_name . '.lock';
772: 
773:        // Try to lock.
774:        $lock_result = $wpdb->query( $wpdb->prepare( "INSERT IGNORE INTO `$wpdb->options` ( `option_name`, `option_value`, `autoload` ) VALUES (%s, %s, 'no') /* LOCK */", $lock_option, time() ) );
775: 
 

Maintenant,si vous le souhaitez,vouspouvez supprimer cette option:

 $>wp option delete core_updater.lock
 

Confirming this 'core_updater.lock'. It may not be obvious at first but look at the line 771.

File: wp-admin/includes/class-wp-upgrader.php
754:    /**
755:     * Creates a lock using WordPress options.
756:     *
757:     * @since 4.5.0
758:     * @access public
759:     * @static
760:     *
761:     * @param string $lock_name       The name of this unique lock.
762:     * @param int    $release_timeout Optional. The duration in seconds to respect an existing lock.
763:     *                                Default: 1 hour.
764:     * @return bool False if a lock couldn't be created or if the lock is no longer valid. True otherwise.
765:     */
766:    public static function create_lock( $lock_name, $release_timeout = null ) {
767:        global $wpdb;
768:        if ( ! $release_timeout ) {
769:            $release_timeout = HOUR_IN_SECONDS;
770:        }
771:        $lock_option = $lock_name . '.lock';
772: 
773:        // Try to lock.
774:        $lock_result = $wpdb->query( $wpdb->prepare( "INSERT IGNORE INTO `$wpdb->options` ( `option_name`, `option_value`, `autoload` ) VALUES (%s, %s, 'no') /* LOCK */", $lock_option, time() ) );
775: 

Now, if you like you may delete this option:

$>wp option delete core_updater.lock

Pourtous ceux qui recherchent la requête MySQL complète:

DELETE FROM wp_options WHERE option_name LIKE '%core_update%' LIMIT 1

For anyone looking for the full MySQL query:

DELETE FROM wp_options WHERE option_name LIKE '%core_update%' LIMIT 1

Dans WordPress,ilexiste deux verrous demise àjour:

• core_updater
• auto_updater

Vouspouvez donc résoudre ceproblèmeen supprimant les verrous demise àjour.

Utilisez le code ci-dessouspour supprimer les verrous:

 delete_option( 'core_updater.lock' );
delete_option( 'auto_updater.lock' );
 

Vouspouvez également supprimer les verrous demise àjour avec la commande CLI.Découvrez comment les supprimer avec la commande CLI .

Utilisez leplugin WordPress entrez la description du lienici fix-update-in-process quimontre les verrousexistantset corrige leproblèmeen un seul clic.

In WordPress there are two update locks:

• core_updater
• auto_updater

So, you can fix this by deleting the update locks.

Use below code to delete the lock's:

delete_option( 'core_updater.lock' );
delete_option( 'auto_updater.lock' );

You can delete the update locks with CLI command too. Checkout how to delete them with CLI command.

Use the WordPress pluginenter link description here fix-update-in-process which show the existing locks and fix the issue with one click.