ማብራሪያ
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/
Screenshots
መጫን
- Install and activate SOS.
- Open SOS in the WordPress admin menu.
- Configure the fallback message, branding, contact details and visitor actions.
- Save the resilience profile.
- Use Preview experience to review the fallback. Preview does not create a real server error.
- Administrators and developers may use the separate controlled fatal test when they need to validate the real failure path.
- Geneva is optional. Connect only if you want the additional connected functionality described above.
SOS will not overwrite an existing third-party wp-content/php-error.php drop-in. If one is present, SOS reports the conflict instead.
የተለመዱ ጥያቄዎች
-
Does SOS fix the fatal error?
-
No. SOS improves the visitor-facing experience while preserving the technical evidence needed to diagnose the underlying problem.
-
Does SOS replace WordPress Recovery Mode?
-
No. WordPress remains responsible for fatal detection and Recovery Mode.
-
Will WordPress still send its critical-error notification email?
-
Yes, where WordPress Recovery Mode would normally send it. SOS replaces only the visitor-facing fatal-error presentation and does not disable or replace WordPress’s recovery email handling.
Email delivery still depends on WordPress identifying an eligible plugin or theme fatal error, the site’s administration email and mail configuration, and WordPress’s built-in email rate limit. Not every type of website outage or fatal error triggers a recovery email.
-
Will SOS work if my theme or a plugin causes a fatal error?
-
Where WordPress’s fatal-error handler can still execute, SOS is designed to render independently of the active theme and has been tested against both plugin-originated and theme-originated fatal errors.
-
Will SOS catch every website outage?
-
No. A WordPress plugin cannot execute in every failure condition. Some failures occur before WordPress or SOS can load or involve infrastructure outside WordPress entirely.
-
Does SOS require Geneva?
-
No. SOS is independently usable. Geneva is an optional external service and is not required for the core fatal-error fallback.
-
Does SOS collect visitor analytics?
-
SOS does not require visitor behavioural analytics for its core functionality. The routine optional Geneva handshake is limited to the installation and technical information described above.
-
Can visitors still contact me?
-
Yes, if you configure a telephone number, email address or alternative route.
-
Can I send visitors to another website or service?
-
Yes. SOS provides up to three optional custom external action buttons.
-
What happens if SOS cannot read its saved branding profile?
-
SOS contains a generic built-in emergency fallback.
-
Will SOS overwrite another php-error.php drop-in?
-
No. SOS reports the conflict and leaves the existing file untouched.
-
Does Preview create a real server error?
-
No. Preview returns a normal response. A separate controlled fatal test is available for administrators and developers who need to validate the real failure path.
-
Where can I get support?
-
Free-plugin support is provided through the SOS support forum on WordPress.org.
Product information and documentation: https://apluskdesign.com/sos/docs/
Support and security enquiries: support@apluskdesign.com
Site-specific WordPress development, hosting, troubleshooting or implementation services are separate from free plugin support.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“SOS – Critical Error Page” is open source software. The following people have contributed to this plugin.
Contributors
Translate “SOS – Critical Error Page” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0
- Initial public release.
- Branded resilient fatal-error experience.
- Preview and controlled administrator testing tools.
- Optional, explicit Geneva connection with public/community handshake support.
- Public-release privacy, terms and external-service disclosures.