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

                    Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

                    Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                    Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020