Make WordPress Core

10/05/2015 03:05:26 PM (9 years ago)

Use wp_installing() instead of WP_INSTALLING constant.

The WP_INSTALLING constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping for
updates, that the normal "not installed" checks should be bypassed, and so on.

A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during wpmu_create_blog() -
for the "installing" flag to be set after WP has already loaded. In these
cases, WP_INSTALLING would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where WP_INSTALLING
was set the first time a site was created, and remained set for the rest of the

The new wp_installing() function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean true or false). Use of
the WP_INSTALLING constant is still supported; wp_installing() will default
to true if the constant is defined during the bootstrap.

Props boonebgorges, jeremyfelt.
See #31130.

1 edited


  • trunk/src/wp-includes/theme.php

    r34554 r34828  
    772772     * @param bool true Validation flag to check the current theme.
    773773     */
    774     if ( defined('WP_INSTALLING') || ! apply_filters( 'validate_current_theme', true ) )
     774    if ( wp_installing() || ! apply_filters( 'validate_current_theme', true ) )
    775775        return true;
Note: See TracChangeset for help on using the changeset viewer.