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;








8















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?










share|improve this question




























    8















    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?










    share|improve this question
























      8












      8








      8


      2






      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?










      share|improve this question














      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 8 at 11:57









      birgirebirgire

      54.5k464150




      54.5k464150




















          1 Answer
          1






          active

          oldest

          votes


















          5














          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






          share|improve this answer

























            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
            );



            );













            draft saved

            draft discarded


















            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









            5














            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






            share|improve this answer





























              5














              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






              share|improve this answer



























                5












                5








                5







                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






                share|improve this answer















                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







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited May 13 at 18:04

























                answered May 8 at 11:57









                birgirebirgire

                54.5k464150




                54.5k464150



























                    draft saved

                    draft discarded
















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

                    Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

                    What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company