Alovio Protect
Fatal-error guard for WordPress
A fatal error, and the visitor still gets the page.
Protect catches a fatal error before WordPress finishes booting, finds the extension that caused it, pauses that one, and replays the request. The visitor waits a moment and gets the page instead of a white screen.
02 — The change
Not recovery mode. Not a rollback.
- 01 Recovery mode Emails you a link and leaves the site downThe visitor waits a moment and gets the page
- 02 Host rollback Restores everything, and loses the orders sincePauses one extension; every order stays
- 03 A database switch Useless when the database is what brokeThe pause lives in files — it works anyway
03 — How it works
What happens in the half-second.
- 01 Caught before boot
The guard runs before WordPress finishes booting, so it sees the fatal before the visitor does.
- 02 Never a database write
The pause is kept in files, not tables — so the guard still works when the database is the thing that broke.
- 03 Integrity
Optional. Every core, plugin and theme file compared with the official WordPress.org checksums.
- 04 Malware, scored
Optional. Each file scored from its token stream rather than matched against a signature list.
- 05 Login hardening
Optional. Failed sign-ins are rate-limited, and the form stops confirming which usernames exist.
04 — In the box
One guard, three optional modules.
- Catches fatals before boot
- Pauses only the culprit
- Replays the request
- State in files, never the database
- Checks against WordPress.org checksums
- Names modified, missing and unexpected files
- Scores token streams, not signatures
- Rate-limits failed sign-ins
- Stops confirming usernames
05 — Questions
Before you decide.
What does it cost?
Nothing. Alovio Protect is free, downloaded from this site, and it updates itself from here afterwards — there is no licence key and no Pro tier waiting behind it.
Isn't this WordPress recovery mode?
No. Recovery mode emails you a link and leaves the site down. Protect serves the visitor the page.
Is it a backup or a rollback?
No. Nothing is restored — one extension is paused — so the orders that arrived since your last snapshot stay.
What if the database is what broke?
The guard keeps its state in files, so it still works.
06 — From the same forge
