IntenseWebs/WordPress
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Introduce filters for skipping parts of the bootstrap process

Browse Source 
Non web interfaces with WordPress (such as wp-cli) need to be able to bypass certain checks in the bootstrap process. This introduces three new filters to allow for those checks to be skipped.

1. Provides a way of forcefully bypassing wp_maintenance().
2. Provides a way of forcefully bypassing wp_debug_mode(). See https://github.com/wp-cli/wp-cli/issues/177
3. Provide a way of forcefully skipping loading wp-content/advance-cache.php. See https://github.com/wp-cli/wp-cli/pull/164

These filters should not be used by plugins (in fact, they run before plugins are loaded, so they can't be used by plugins). In general, they should only be used in non-web interactions with WordPress.

See #34936.
Props jorbin, DrewAPicture.

Built from https://develop.svn.wordpress.org/trunk@37626


git-svn-id: http://core.svn.wordpress.org/trunk@37594 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
Aaron Jorbin
2016-06-02 18:47:27 +00:00
parent e202610ac8
commit cedaaaf779
3 changed files with 43 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
wp-settings.php
View File

@@ -70,8 +70,18 @@ timer_start();
// Check if we're in WP_DEBUG mode.
wp_debug_mode();
/**
* Bypass the loading of advanced-cache.php
*
* This filter should *NOT* be used by plugins. It is designed for non-web
* runtimes. If true is returned, advance-cache.php will never be loaded.
*
* @since 4.6.0
*
* @param bool True to bypass advanced-cache.php
*/
if ( WP_CACHE && ! apply_filters( 'bypass_advanced_cache', false ) ) {
// For an advanced caching plugin to use. Uses a static drop-in because you would only want one.
if ( WP_CACHE ) {
_backup_plugin_globals();
WP_DEBUG ? include( WP_CONTENT_DIR . '/advanced-cache.php' ) : @include( WP_CONTENT_DIR . '/advanced-cache.php' );
_restore_plugin_globals();