Getting Started - apluskdesign

SOS Documentation

Good to knowSOS works immediately after activation with sensible defaults. You do not need to connect an account, enter a licence key or use an external service before SOS can provide its core functionality.

SOS – Critical Error Page provides an alternative visitor-facing experience when WordPress encounters a supported fatal error.Once activated, SOS prepares a local version of your Critical Error Page so that it can remain available even when parts of your normal WordPress website may not be.SOS does not repair the underlying error and does not replace WordPress Recovery Mode. Its job is to look after the visitor experience while the underlying problem is investigated.

Install SOS

SOS can be installed through the WordPress administration area like any other WordPress plugin.

Once SOS is available from the WordPress Plugin Directory:

Sign in to your WordPress administration area.
Go to Plugins → Add New Plugin.
Search for apluskdesign SOS – Critical Error Page.
Select Install Now.
When installation has completed, select Activate.

After activation, a new SOS destination will appear in your WordPress administration menu.

Screenshot: SOS in WordPress administration

SOS appears in the WordPress administration menu after activation.

What happens when SOS is activated?

SOS prepares the files and information required to provide your Critical Error Page if WordPress later encounters a supported fatal error.

You do not need to create an account, enter a licence key or connect to an external service before SOS can provide its core functionality.

SOS is designed to work independently.

During setup, SOS also checks whether the WordPress fatal-error drop-in location is available before managing its own Critical Error Page.

If SOS finds an existing drop-in that it does not own, it will not silently overwrite or remove it.

Learn more about how SOS works

Open SOS

Select SOS from the WordPress administration menu to open the main SOS screen.

This is where you can configure the visitor-facing information used by your Critical Error Page and review the current SOS status.

Screenshot: Main SOS configuration screen

The main SOS screen lets you configure the visitor-facing Critical Error Page.

Set up your Critical Error Page

SOS includes sensible defaults so that the Critical Error Page can be prepared without requiring a complicated setup process.

You can personalise the experience to suit your website or business, including the information and presentation available in your SOS settings.

The aim is simple: if something goes wrong with WordPress, visitors should receive a clear and useful explanation rather than being left wondering whether the website has disappeared.

Keep it simpleVisitors do not need technical information about PHP, plugins or the underlying fatal error. A calm explanation and a useful next action are usually enough.

Set up your Critical Error Page

Save your settings

After configuring SOS, save your changes normally.

SOS uses the current configuration to prepare its local resilience profile. This contains the information needed for the emergency visitor experience without requiring the normal website to build the page at the point of failure.

This is an important part of how SOS is designed to remain useful during a fatal condition.

Learn about the SOS resilience profile

Test SOS

Once your Critical Error Page is configured, you can use the controlled fatal test available in SOS Developer Tools to confirm the emergency experience is working.

The test lets you see what a visitor would receive without deliberately installing broken software or damaging your website.

ImportantUse the controlled test provided by SOS rather than deliberately editing WordPress, plugin or theme files to create a real fatal error.

During the test you should see the Critical Error Page you have configured. Afterwards, you should be able to return to your normal website and WordPress administration area.

Learn how to test SOS safely

WordPress Recovery Mode still works normally

SOS does not replace or disable WordPress Recovery Mode.

WordPress remains responsible for detecting the fatal error and providing its normal recovery mechanisms to administrators. SOS concentrates on what the visitor receives while the website is experiencing the problem.

SOS looks after the visitor experience. WordPress looks after the error.

WordPress Recovery Mode & SOS

Connecting to Geneva is optional

You may see an option to connect SOS to Geneva.

Geneva is an optional apluskdesign service that can provide additional installation and product context.

Geneva is optionalYou do not need to connect SOS to Geneva for your Critical Error Page to work. SOS remains independently useful without a Geneva connection.

Before connecting, SOS provides information about the connection and the applicable terms so that an administrator can make a deliberate choice.

Learn about connecting SOS to Geneva

Privacy & data

SOS is designed around data minimisation.

Its core Critical Error Page functionality operates locally on your WordPress installation and does not require visitor analytics, an external account or a remote service.

If you choose to enable an optional integration such as Geneva, additional installation information may be exchanged as described in the relevant documentation and privacy information.

Read about SOS Privacy & Data