How to disable the fatal error (WSOD) protection?Fatal error: Call to undefined function is_multisite()Fatal error with a themeFatal Error: get_header();Child Theme Fatal ErrorCatchable fatal error in formatting.phpFatal error due to file permissionsFatal error post.php help :(Fatal error: Call to undefined function wp_raise_memory_limit()Problem: Fatal error worldpress themeFatal error: require(): Failed opening required 'WP_DIRwp-blog-header.php'
nginx conf: http2 module not working in Chrome in ubuntu 18.04
Wifi light switch needs neutral wire. Why? AND Can that wire be a skinny one?
Variable does not Exist: CaseTrigger
Real Analysis: Proof of the equivalent definitions of the derivative.
Is there a word for pant sleeves?
Existence of a model of ZFC in which the natural numbers are really the natural numbers
Why is this python script running in background consuming 100 % CPU?
How does the Earth's center produce heat?
If change in free energy (G) is positive, how do those reactions still occur?
Writing "hahaha" versus describing the laugh
Download app bundles from App Store to run on iOS Emulator on Mac
How to safely discharge oneself
Adobe Illustrator: How can I change the profile of a dashed stroke?
What pc resources are used when bruteforcing?
One word for 'the thing that attracts me'?
Has the wall been repaired?
How do I write real-world stories separate from my country of origin?
How to tease a romance without a cat and mouse chase?
Is a world with one country feeding everyone possible?
Why do the i8080 I/O instructions take a byte-sized operand to determine the port?
Can a UK national work as a paid shop assistant in the USA?
amsmath: How can I use the equation numbering and label manually and anywhere?
Meaning of "half-crown enclosure"
Salesforce bug enabled "Modify All"
How to disable the fatal error (WSOD) protection?
Fatal error: Call to undefined function is_multisite()Fatal error with a themeFatal Error: get_header();Child Theme Fatal ErrorCatchable fatal error in formatting.phpFatal error due to file permissionsFatal error post.php help :(Fatal error: Call to undefined function wp_raise_memory_limit()Problem: Fatal error worldpress themeFatal error: require(): Failed opening required 'WP_DIRwp-blog-header.php'
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
The fatal error handling was introduced in WordPress 5.1 and 5.2.
It's sometimes referred to as the White Screen Of Death (WSOD) protection.
When working on dev/local installs, we sometimes want to be able to break the sites as needed, and e.g. avoid the email recovery process for the site when working within a protected endpoint (see is_protected_endpoint()
):
The site is experiencing technical difficulties. Please check your
site admin email inbox for instructions.
How can we disable the fatal error handling?
errors
add a comment |
The fatal error handling was introduced in WordPress 5.1 and 5.2.
It's sometimes referred to as the White Screen Of Death (WSOD) protection.
When working on dev/local installs, we sometimes want to be able to break the sites as needed, and e.g. avoid the email recovery process for the site when working within a protected endpoint (see is_protected_endpoint()
):
The site is experiencing technical difficulties. Please check your
site admin email inbox for instructions.
How can we disable the fatal error handling?
errors
add a comment |
The fatal error handling was introduced in WordPress 5.1 and 5.2.
It's sometimes referred to as the White Screen Of Death (WSOD) protection.
When working on dev/local installs, we sometimes want to be able to break the sites as needed, and e.g. avoid the email recovery process for the site when working within a protected endpoint (see is_protected_endpoint()
):
The site is experiencing technical difficulties. Please check your
site admin email inbox for instructions.
How can we disable the fatal error handling?
errors
The fatal error handling was introduced in WordPress 5.1 and 5.2.
It's sometimes referred to as the White Screen Of Death (WSOD) protection.
When working on dev/local installs, we sometimes want to be able to break the sites as needed, and e.g. avoid the email recovery process for the site when working within a protected endpoint (see is_protected_endpoint()
):
The site is experiencing technical difficulties. Please check your
site admin email inbox for instructions.
How can we disable the fatal error handling?
errors
errors
asked May 8 at 11:57
birgirebirgire
54.5k464150
54.5k464150
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
We can modify the bool output of the wp_is_fatal_error_handler_enabled()
function in two ways:
Constant
Set the WP_DISABLE_FATAL_ERROR_HANDLER
constant to true
within the wp-config.php
file:
/**
* Disable the fatal error handler.
*/
const WP_DISABLE_FATAL_ERROR_HANDLER = true;
or
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
Filter
Use wp_fatal_error_handler_enabled
bool filter:
/**
* Disable the fatal error handler.
*/
add_filter( 'wp_fatal_error_handler_enabled', '__return_false' );
Notes
See ticket #44458
The wp_fatal_error_handler_enabled
filter will override the value of the WP_DISABLE_FATAL_ERROR_HANDLER
constant.
Also watch out for a possible bool confusion with the constant disabling but the filter enabling.
In my testing the filter approach, as a must-use plugin, is not working as expected, so I'm using the constant instead. Hopefully I can look into this further.
One can also add a custom drop-in file fatal-error-handler.php
into the wp-content
directory (src), to override the WP_Fatal_Error_Handler
class as needed. We must use a different class name and it must define the handle()
method as the registered shutdown function.
A simple example to disable it would be to override the default error handler class with a custom one that does nothing:
<?php
class WPSE_Fatal_Error_Handler
public function handle()
return new WPSE_Fatal_Error_Handler;
Anonymous class in PHP 7+ seems to work as well:
<?php
return new Class()
public function handle()
;
It could also extend the default WP_Fatal_Error_Handler
class if needed.
Then there's the WP_SANDBOX_SCRAPING
constant. See #46045
Setting the WP_DEBUG
as true will not disable the WSOD protection. This is by design. See #46825
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "110"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwordpress.stackexchange.com%2fquestions%2f337391%2fhow-to-disable-the-fatal-error-wsod-protection%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
We can modify the bool output of the wp_is_fatal_error_handler_enabled()
function in two ways:
Constant
Set the WP_DISABLE_FATAL_ERROR_HANDLER
constant to true
within the wp-config.php
file:
/**
* Disable the fatal error handler.
*/
const WP_DISABLE_FATAL_ERROR_HANDLER = true;
or
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
Filter
Use wp_fatal_error_handler_enabled
bool filter:
/**
* Disable the fatal error handler.
*/
add_filter( 'wp_fatal_error_handler_enabled', '__return_false' );
Notes
See ticket #44458
The wp_fatal_error_handler_enabled
filter will override the value of the WP_DISABLE_FATAL_ERROR_HANDLER
constant.
Also watch out for a possible bool confusion with the constant disabling but the filter enabling.
In my testing the filter approach, as a must-use plugin, is not working as expected, so I'm using the constant instead. Hopefully I can look into this further.
One can also add a custom drop-in file fatal-error-handler.php
into the wp-content
directory (src), to override the WP_Fatal_Error_Handler
class as needed. We must use a different class name and it must define the handle()
method as the registered shutdown function.
A simple example to disable it would be to override the default error handler class with a custom one that does nothing:
<?php
class WPSE_Fatal_Error_Handler
public function handle()
return new WPSE_Fatal_Error_Handler;
Anonymous class in PHP 7+ seems to work as well:
<?php
return new Class()
public function handle()
;
It could also extend the default WP_Fatal_Error_Handler
class if needed.
Then there's the WP_SANDBOX_SCRAPING
constant. See #46045
Setting the WP_DEBUG
as true will not disable the WSOD protection. This is by design. See #46825
add a comment |
We can modify the bool output of the wp_is_fatal_error_handler_enabled()
function in two ways:
Constant
Set the WP_DISABLE_FATAL_ERROR_HANDLER
constant to true
within the wp-config.php
file:
/**
* Disable the fatal error handler.
*/
const WP_DISABLE_FATAL_ERROR_HANDLER = true;
or
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
Filter
Use wp_fatal_error_handler_enabled
bool filter:
/**
* Disable the fatal error handler.
*/
add_filter( 'wp_fatal_error_handler_enabled', '__return_false' );
Notes
See ticket #44458
The wp_fatal_error_handler_enabled
filter will override the value of the WP_DISABLE_FATAL_ERROR_HANDLER
constant.
Also watch out for a possible bool confusion with the constant disabling but the filter enabling.
In my testing the filter approach, as a must-use plugin, is not working as expected, so I'm using the constant instead. Hopefully I can look into this further.
One can also add a custom drop-in file fatal-error-handler.php
into the wp-content
directory (src), to override the WP_Fatal_Error_Handler
class as needed. We must use a different class name and it must define the handle()
method as the registered shutdown function.
A simple example to disable it would be to override the default error handler class with a custom one that does nothing:
<?php
class WPSE_Fatal_Error_Handler
public function handle()
return new WPSE_Fatal_Error_Handler;
Anonymous class in PHP 7+ seems to work as well:
<?php
return new Class()
public function handle()
;
It could also extend the default WP_Fatal_Error_Handler
class if needed.
Then there's the WP_SANDBOX_SCRAPING
constant. See #46045
Setting the WP_DEBUG
as true will not disable the WSOD protection. This is by design. See #46825
add a comment |
We can modify the bool output of the wp_is_fatal_error_handler_enabled()
function in two ways:
Constant
Set the WP_DISABLE_FATAL_ERROR_HANDLER
constant to true
within the wp-config.php
file:
/**
* Disable the fatal error handler.
*/
const WP_DISABLE_FATAL_ERROR_HANDLER = true;
or
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
Filter
Use wp_fatal_error_handler_enabled
bool filter:
/**
* Disable the fatal error handler.
*/
add_filter( 'wp_fatal_error_handler_enabled', '__return_false' );
Notes
See ticket #44458
The wp_fatal_error_handler_enabled
filter will override the value of the WP_DISABLE_FATAL_ERROR_HANDLER
constant.
Also watch out for a possible bool confusion with the constant disabling but the filter enabling.
In my testing the filter approach, as a must-use plugin, is not working as expected, so I'm using the constant instead. Hopefully I can look into this further.
One can also add a custom drop-in file fatal-error-handler.php
into the wp-content
directory (src), to override the WP_Fatal_Error_Handler
class as needed. We must use a different class name and it must define the handle()
method as the registered shutdown function.
A simple example to disable it would be to override the default error handler class with a custom one that does nothing:
<?php
class WPSE_Fatal_Error_Handler
public function handle()
return new WPSE_Fatal_Error_Handler;
Anonymous class in PHP 7+ seems to work as well:
<?php
return new Class()
public function handle()
;
It could also extend the default WP_Fatal_Error_Handler
class if needed.
Then there's the WP_SANDBOX_SCRAPING
constant. See #46045
Setting the WP_DEBUG
as true will not disable the WSOD protection. This is by design. See #46825
We can modify the bool output of the wp_is_fatal_error_handler_enabled()
function in two ways:
Constant
Set the WP_DISABLE_FATAL_ERROR_HANDLER
constant to true
within the wp-config.php
file:
/**
* Disable the fatal error handler.
*/
const WP_DISABLE_FATAL_ERROR_HANDLER = true;
or
define( 'WP_DISABLE_FATAL_ERROR_HANDLER', true );
Filter
Use wp_fatal_error_handler_enabled
bool filter:
/**
* Disable the fatal error handler.
*/
add_filter( 'wp_fatal_error_handler_enabled', '__return_false' );
Notes
See ticket #44458
The wp_fatal_error_handler_enabled
filter will override the value of the WP_DISABLE_FATAL_ERROR_HANDLER
constant.
Also watch out for a possible bool confusion with the constant disabling but the filter enabling.
In my testing the filter approach, as a must-use plugin, is not working as expected, so I'm using the constant instead. Hopefully I can look into this further.
One can also add a custom drop-in file fatal-error-handler.php
into the wp-content
directory (src), to override the WP_Fatal_Error_Handler
class as needed. We must use a different class name and it must define the handle()
method as the registered shutdown function.
A simple example to disable it would be to override the default error handler class with a custom one that does nothing:
<?php
class WPSE_Fatal_Error_Handler
public function handle()
return new WPSE_Fatal_Error_Handler;
Anonymous class in PHP 7+ seems to work as well:
<?php
return new Class()
public function handle()
;
It could also extend the default WP_Fatal_Error_Handler
class if needed.
Then there's the WP_SANDBOX_SCRAPING
constant. See #46045
Setting the WP_DEBUG
as true will not disable the WSOD protection. This is by design. See #46825
edited May 13 at 18:04
answered May 8 at 11:57
birgirebirgire
54.5k464150
54.5k464150
add a comment |
add a comment |
Thanks for contributing an answer to WordPress Development Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwordpress.stackexchange.com%2fquestions%2f337391%2fhow-to-disable-the-fatal-error-wsod-protection%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown