Al Amin

<blockquote>
<p>Professional-grade fatal error protection for WordPress websites.</p>
</blockquote>
<p>When a plugin update fails or your database server goes offline, most WordPress sites collapse into a broken white screen or generic server error. This hurts customer trust, interrupts sales, and can negatively impact SEO crawling.</p>
<p><strong>FatalFlow</strong> intercepts fatal PHP and database failures <em>before WordPress fully loads</em>, displaying a clean branded recovery page instead of a broken website.</p>
<p>Perfect for agencies, WooCommerce stores, business websites, and production environments.</p>
<h3>Why FatalFlow?</h3>
<h3>Protect Your SEO Rankings</h3>
<p>FatalFlow returns a proper:</p>
<pre><code>503 Service Unavailable
</code></pre>
<p>response with a <code>Retry-After</code> header — helping search engines understand that your site is temporarily unavailable instead of permanently broken.</p>
<p>This helps reduce the risk of:<br />
– Google de-indexing<br />
– SEO ranking drops<br />
– Crawling issues caused by 500 errors</p>
<h3>Prevent the “White Screen of Death”</h3>
<p>Instead of exposing visitors to raw PHP fatal errors or blank pages, FatalFlow shows:<br />
– a professional maintenance screen,<br />
– loading indicator,<br />
– branded messaging,<br />
– modern glassmorphism UI.</p>
<h3>Works Even When WordPress Fails</h3>
<p>FatalFlow operates using:<br />
– MU-plugin recovery logic<br />
– <code>db-error.php</code> drop-ins<br />
– shutdown fatal handlers</p>
<p>This means protection still works when:<br />
– plugins crash,<br />
– themes break,<br />
– database connections fail,<br />
– WordPress core cannot fully boot.</p>
<h3>Features</h3>
<p>  Feature<br />
  Details</p>
<p>  Fatal error protection<br />
  Handles <code>E_ERROR</code>, <code>E_PARSE</code>, <code>E_CORE_ERROR</code>, <code>E_COMPILE_ERROR</code></p>
<p>  Database outage recovery<br />
  Automatic <code>db-error.php</code> deployment</p>
<p>  SEO-safe maintenance mode<br />
  Sends proper <code>503</code> headers</p>
<p>  Zero dependency architecture<br />
  Works without database or active plugins</p>
<p>  Lightweight performance<br />
  No frontend slowdown during normal operation</p>
<p>  Beautiful recovery UI<br />
  Modern dark glassmorphism maintenance screen</p>
<p>  WP-CLI aware<br />
  Automatically skips handlers during CLI operations</p>
<p>  Safe cleanup<br />
  Removes generated files on deactivation</p>
<h3>Technical Highlights</h3>
<ul>
<li>System-level recovery architecture</li>
<li>Early bootstrap interception</li>
<li>Automatic MU-plugin deployment</li>
<li>Database-independent rendering</li>
<li>Clean activation & deactivation flow</li>
<li>Minimal runtime overhead</li>
</ul>


FatalFlow – WordPress Fatal Error Recovery & SEO Protection

Protect your WordPress website from fatal errors, database crashes, and SEO damage with an instant recovery maintenance UI.

luciano-croce

<p>Dismiss <em>coming soon</em> “<strong>WSoD</strong>” Protection (White Screen of Death) when it is activated, or if it is in mu-plugins directory.</p>
<p>Development takes place at <a href="https://github.com/luciano-croce/dismiss-wsod-protection/" rel="nofollow ugc">GitHub</a> and <a href="https://travis-ci.org/luciano-croce/dismiss-wsod-protection/" rel="nofollow ugc">Travis CI</a>.</p>
<p>Compatible with <a href="https://translate.wordpress.org/projects/wp-plugins/dismiss-wsod-protection/" rel="nofollow ugc">GlotPress Translations</a>.</p>
<p>Approved in the repository of the plugin directory on 2019-02-01</p>
<blockquote>
<p>this plugin use <a href="https://semver.org/" rel="nofollow ugc">Semantic Versioning</a> MAJOR.MINOR.PATCH</p>
</blockquote>
<h4>Because I made this?</h4>
<ul>
<li>If you are not “interested” in this feature.</li>
<li>For security purpose. Read more on <a href="https://www.zdnet.com/article/concerns-raised-about-wordpress-new-white-screen-of-death-protection-feature/" rel="nofollow ugc">ZDNet here</a> and <a href="https://make.wordpress.org/core/2019/01/14/php-site-health-mechanisms-in-5-1/" rel="nofollow ugc">Felix Arntz here</a>.</li>
<li>White Screen of Death (WSoD) was posponed to WP 5.2 instead of 5.1</li>
</ul>
<p>Also consult the Codex about how to “fix” the <a href="https://codex.wordpress.org/Common_WordPress_Errors/" rel="nofollow ugc">White Screen of Death</a>.</p>
<h4>Tips</h4>
<p>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!</p>
<p>Also, for translation functionality, put all files of the single languages (dismiss-wsod-protection-en_US.mo 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!</p>
<p>Note that mu-plugins functionality is available since WP 2.8+ or greater and is not present in WP 2.7+ or previous.</p>
<h4>About it</h4>
<p>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.</p>
<blockquote>
<p>super light secure and fast plugin easy on server resources</p>
</blockquote>
<h4>About me</h4>
<p>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 WordPress.org & Plugins & Themes Directory, Local Manager of Ligurian Language Community for WP LIJ, Validator English (UK) for WordPress.com, 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.</p>
<h4>Translation</h4>
<p>Translated by: <a href="https://profiles.wordpress.org/luciano-croce/" rel="nofollow ugc">Luciano Croce</a></p>
<p>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!</p>
<h4>Disclaimer</h4>
<p>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.</p>
<h4>Privacy</h4>
<p>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.</p>
<h4>GDPR</h4>
<p>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.</p>


Dismiss WSoD Protection

dismiss wordpress wsod (white screen of death) protection introduced in wp 5.1-beta1 for security purpose -- By Luciano Croce

FatalFlow – WordPress Fatal Error Recovery & SEO Protection vs Dismiss WSoD Protection