{"id":5,"date":"2026-09-23T17:10:27","date_gmt":"2026-09-23T17:10:27","guid":{"rendered":"https:\/\/demo.alovio.org\/protect\/try-it\/"},"modified":"2026-09-23T17:10:27","modified_gmt":"2026-09-23T17:10:27","slug":"try-it","status":"publish","type":"page","link":"https:\/\/demo.alovio.org\/protect\/","title":{"rendered":"Break this site"},"content":{"rendered":"\n
\n\n

Live demo<\/p>\n\n

This site is running Alovio Protect.
Try to take it down.<\/h2>\n\n

There is a plugin installed here called Demo: Breakable Plugin<\/strong>. It does nothing at all until you press the button below \u2014 and then it fails the way a bad update fails, with a fatal error that normally ends the request and leaves a visitor staring at a blank white page.<\/p>\n\n

Break this site \u2192<\/a><\/p>\n\n

Nothing here is yours and everything resets on the hour, so press it as often as you like.<\/p>\n\n

What happens when you do<\/h3>\n\n
    \n
  1. First press.<\/strong> The crash is caught. You get a short holding page instead of a white screen, and the failure is recorded with the plugin that caused it named.<\/li>\n
  2. Second press.<\/strong> The same plugin has now failed twice, so it is paused and the request is replayed without it. The page loads. The rest of the site was never affected.<\/li>\n
  3. Pausing does not touch the database. WordPress still lists the plugin as active \u2014 it is filtered out while the page is built, which is why putting it back is one click and nothing was rewritten behind your back.<\/li>\n <\/ol>\n\n

    Then look at the admin<\/h3>\n\n

    You are signed in already. The dashboard shows the crash you just caused, and four other things that are real rather than staged on this install:<\/p>\n\n