This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Dismiss WSoD Protection


Dismiss coming soonWSoD” Protection (White Screen of Death) when it is activated, or if it is in mu-plugins directory.

Development takes place at GitHub and Travis CI.

Compatible with GlotPress Translations.

Approved in the repository of the plugin directory on 2019-02-01

this plugin use Semantic Versioning MAJOR.MINOR.PATCH

Because I made this?

  • If you are not “interested” in this feature.
  • For security purpose. Read more on ZDNet here and Felix Arntz here.
  • White Screen of Death (WSoD) was posponed to WP 5.2 instead of 5.1

Also consult the Codex about how to “fix” the White Screen of Death.


A neat trick, is to put this single file dismiss-wsod-protection.php (not its parent directory) in the /wp-content/mu-plugins/ directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!

Also, for translation functionality, put all files of the single languages ( for example) that you need (not its parent directory) in the /wp-content/mu-plugins/ directory (create it if not exists) and will also be loaded by default, since first step installation of WordPress setup!

Note that mu-plugins functionality is available since WP 2.8+ or greater and is not present in WP 2.7+ or previous.

About it

The code of this plugin is not written with a PHP framework, but manually, with a simple PHP editor compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor. This author is exonerated from any responsibility or damage (directly or indirectly) caused and due to the use of this bad practice.

super light secure and fast plugin easy on server resources

About me

Dismiss WSoD Protection is developed by Luciano Croce, 13-years “officially” WordPress Plugins & Themes Developer Senior, Co-Author of plugin Classic Editor, polyglot (based on English, French, Spanish, German, Portuguese, Italian, Ligurian), Local Manager of WP Community Ligurian Language LIJ, GTE en_GB & en_CA, CLPTE for en_AU, PTE for Plugins & Themes in more other languages, PTE for Italian & Plugins & Themes Directory, Local Manager of Ligurian Language Community for WP LIJ, Validator English (UK) for, translator for my & other projects, book author of TRUE DOS (the dark side of its history from the dark side of its users) Code Tweaker & Bug Hunter, Security Mechanic & WPMU Lover, Freelancer & Volunteer.


Translated by: Luciano Croce

Translators, except the similar strings “Release Date: February 01, 2019” or strings before latest version number “1.0.0” (for example), remember to leave all the other changelog strings commented in GlotPress “Meta” as “Found in changelog list item section” in english (copy from original -> suggest new translation) according to my disclaimer (read it after this section) all contributes are appreciated, and are credited!


Given that the more languages in which the readme.txt file is translated, the greater the possibility of reaching a larger number of people, even through the use of search engines, with the exception of the main descriptions, it is a good practice, not to translate the changelog of the file readme.txt file in the various languages different from en_US (except for the other English languages derived from English – this is not a rule – everyone is free to translate or not translate according to the indications of their own polyglots community) to standardize the understanding of its technical content, and not to introduce new errors due to the misunderstanding of its correct translation. It should also be added that a good compilation of it can be represented by the perspective of offering the best description possible on what it does, on its characteristics, and its functioning. This does not represent a condition / suggestion, but it indicates the motivation for which the changelog of this plugin was left in English.


This plugin does not collect or store any user related data or personally identifying information, does not set any cookies, and it does not connect to any third-party websites. It only uses functionality that is available in WordPress. In those terms, it does not affect your website users’ privacy in any way.


This plugin does not collect or store any user related data or personally identifying information, but does not do anything to make your site less GDPR compliant. I have done my best to ensure that is 100% GDPR compliant, but I’m not a lawyer, so can’t guarantee anything. To determine if your site is GDPR compliant, please consult a lawyer.


  • Screenshot 1 of 4 “Dismiss WSoD Protection”
  • Screenshot 2 of 4 “Dismiss WSoD Protection”
  • Screenshot 3 of 4 “Dismiss WSoD Protection”
  • Screenshot 4 of 4 “Dismiss WSoD Protection”


There are no reviews for this plugin.

Contributors & Developers

“Dismiss WSoD Protection” is open source software. The following people have contributed to this plugin.


“Dismiss WSoD Protection” has been translated into 6 locales. Thank you to the translators for their contributions.

Translate “Dismiss WSoD Protection” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.


Approved in the plugin directory on 2019-02-01

Detailed changes are available on GitHub.


Release Date: February 01, 2019

  • Public initial commit


Release Date: February 01, 2019

  • GitHub initial commit