SOS – Critical Error Page

WordPress can fail without your business looking broken.

SOS replaces WordPress’s generic visitor-facing critical-error experience with a calm, branded and useful fallback while preserving the technical evidence administrators and developers need to diagnose the underlying problem.

The machinery may fail. The experience should remain professional.

SOS does not fix or suppress the fatal error. WordPress Recovery Mode, PHP logging and developer diagnostics remain available. SOS cannot intercept every possible WordPress, PHP, server, database, network or hosting failure; some failures occur before WordPress or SOS can load.

Product information and documentation: https://apluskdesign.com/sos/docs/

Visitor continuity

SOS can display your site or business name, logo, custom wording, brand colours, a background image or repeating pattern, safe typography, telephone number, email address, Retry and Homepage actions, an optional contact or help route, and up to three custom external actions.

Visitors can still call, email, book elsewhere, visit an alternative service or follow another useful route while the normal website is unavailable.

Resilient by design

During fatal rendering, SOS does not require the active theme, a page builder, JavaScript, a remote API, a database query, Geneva or another apluskdesign product.

SOS uses a small compiled resilience profile. If that profile is unavailable, SOS contains a generic built-in emergency fallback.

Recovery Mode and diagnostics

SOS changes the visitor presentation. It does not suppress the underlying fatal error. WordPress remains responsible for fatal detection and Recovery Mode.

Optional Geneva connection

SOS works independently without Geneva.

An authorised WordPress administrator may deliberately choose to connect SOS to Geneva, an external service operated by apluskdesign. SOS does not contact Geneva merely because the capability exists.

When connected, SOS sends limited installation and technical information so Geneva can identify and support the installation and provide compatible connected functionality. This includes:

• SOS product identity and installed version;
• a persistent local installation identifier;
• the website URL;
• WordPress environment type;
• WordPress version;
• PHP version;
• declared SOS/Geneva capabilities; and
• applicable SOS/Geneva service-terms version and acceptance evidence.

Routine SOS/Geneva handshakes are not intended to transmit visitor behavioural analytics, visitor personal information, visitor cookies, request payloads, website-user credentials, authentication credentials, filesystem paths, PHP stack traces or unnecessary fatal-error diagnostic information.

The Geneva connection is optional. Disconnecting stops SOS’s routine connected relationship with Geneva; SOS core functionality continues independently. Limited historical service records may be retained as described in the privacy information and terms.

Service: https://apluskdesign.com/
Privacy information: https://apluskdesign.com/privacy-cookie-policy/
SOS Terms of Use: https://apluskdesign.com/sos/terms-conditions/

Privacy

SOS does not track visitors and does not require a remote service to provide its core fatal-error fallback.

Administrators may choose to configure public business information such as a telephone number, email address, logo or external links. This information is intentionally shown to visitors when SOS renders.

If an administrator deliberately enables the optional Geneva connection, limited installation and technical information is sent to apluskdesign as described above. SOS also provides suggested text in WordPress’s Privacy Policy Guide to help site administrators document the optional Geneva connection where appropriate.

Privacy information: https://apluskdesign.com/privacy-cookie-policy/