#2974 - panic.php
-
By PDStig
- Added
- 2 views
| Identifier | #2974 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | panic.php |
| Status | Closed (no changes needed) |
| Handling member | Chris Graham |
| Addon | core |
| Description | So I like how the composr system has several different preventive features, such as failover mode as well as the upgrader and such being run on a minimal Composr system. However, there isn't enough isolation when something very bad happens on a Composr website.
For instance, just recently I had to remove a custom startup hook as it was destroying the format of email notifications. But self-learning cache didn't pick up on this correctly and caused everything to start erroring saying the custom hook is missing or corrupt. No biggie, I thought. I'd go in the upgrader script and clear the cache. Problem is this also caused the upgrader script to not work as well. So I had to send the site into failover mode, manually delete all the cache files, ensure no references to the hook exist anywhere in the database, and then bring the site back. I would like to recommend a feature, such as panic.php. This script exists in the root directory of Composr and utilizes _config.php's master password. It does NOT utilize ANY of Composr's systems; it is an almost completely independent script apart from needing _config.php for the master password. Accessing the script asks for the master password and a final confirmation to send the website into panic mode (panic mode could be your choosing... either activation of failover mode, activation of dev mode, activation of safe mode, causing the website to bypass all Composr systems and instead load a special 503 HTML page, etc.). And, of course, panic mode can be undone when the issue is fixed. Perhaps panic.php could also contain some useful dev tools for force-fixing a problem, such as deleting all files in the caches folder or in the caches database tables, inspecting the error log file, sending composr into safe mode, anything you think would be useful debugging or emergency fixing tools. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
I will, however, open a new documentation issue to improve the tut_disaster tutorial.