Core updates: Explicitly call wp_cache_delete() after a DB upgrade, as not all cache backends allow the entire backend to be flushed.
props dd32. fixes #26173. git-svn-id: https://develop.svn.wordpress.org/trunk@26734 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
parent
8aa177267e
commit
bb59e40a22
@ -894,6 +894,8 @@ function update_core($from, $to) {
|
|||||||
|
|
||||||
// Clear the cache to prevent an update_option() from saving a stale db_version to the cache
|
// Clear the cache to prevent an update_option() from saving a stale db_version to the cache
|
||||||
wp_cache_flush();
|
wp_cache_flush();
|
||||||
|
// (Not all cache backends listen to 'flush')
|
||||||
|
wp_cache_delete( 'alloptions', 'options' );
|
||||||
|
|
||||||
// Remove working directory
|
// Remove working directory
|
||||||
$wp_filesystem->delete($from, true);
|
$wp_filesystem->delete($from, true);
|
||||||
|
Loading…
Reference in New Issue
Block a user