=== NaveenCodes Safe Mode ===
Contributors: shinu1503
Tags: safe mode, fatal error, recovery, plugin recovery, theme recovery
Requires at least: 6.5
Tested up to: 7.0
Requires PHP: 8.0
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Emergency recovery layer for WordPress fatal plugin and theme errors.

== Description ==

NaveenCodes Safe Mode helps restore access after fatal plugin or theme crashes. It detects fatal PHP shutdown errors, identifies whether the source is a plugin or theme, performs the configured recovery action, records detailed logs, stores recovery history, shows persistent admin notices, and emails administrators.

The plugin does not modify, rewrite, or repair user code. Version 1 is focused only on detection, disabling, recovery, logging, and notification.

== Version 1 Architecture ==

* Namespace: `NaveenCodes\SafeMode`
* Prefix: `ncsm_`
* Text domain: `naveencodes-safe-mode`
* Bootstrap: `naveencodes-safe-mode.php`
* Autoloading: lightweight PSR-4 style autoloader for `includes/`
* Composition root: `includes/Core/Plugin.php`
* Service boundaries:
  * `Core`: activation, deactivation, settings, plugin bootstrapping
  * `Database`: custom table schema
  * `Recovery`: shutdown detection, source detection, queueing, plugin/theme recovery, notifications
  * `Logging`: error logs and recovery history persistence
  * `Admin`: dashboard, logs, history, settings, notices, coming soon UI
  * `Helpers`: focused WordPress helper utilities
  * `Interfaces`: shared service contracts

== Database Schema ==

`wp_ncsm_logs`

* `id`
* `timestamp`
* `error_type`
* `error_message`
* `file_path`
* `line_number`
* `source_type`
* `source_name`
* `action_taken`
* `recovery_status`

`wp_ncsm_recovery_history`

* `id`
* `timestamp`
* `source_type`
* `source_name`
* `recovery_action`
* `recovery_result`

== Recovery Workflow ==

1. Register a shutdown function early on `plugins_loaded`.
2. Inspect `error_get_last()` on shutdown.
3. Continue only for fatal, parse, compile, core, user, or recoverable fatal errors.
4. Detect source from the error file path:
   * `wp-content/plugins/...` becomes a plugin source.
   * `wp-content/themes/...` becomes a theme source.
   * Anything else is stored as Unknown Source.
5. Check recovery queue attempts for the source.
6. If the source is a plugin and plugin auto-disable is enabled, deactivate the faulty plugin.
7. If the source is the active theme and theme recovery is enabled, switch to the configured fallback theme.
8. Log the error and recovery action.
9. Store recovery history.
10. Add a persistent admin notice.
11. Send an administrator email when enabled.

== WordPress Hooks ==

* `plugins_loaded` boots the plugin.
* `register_shutdown_function()` detects fatal shutdown errors.
* `admin_menu` registers the admin pages.
* `admin_enqueue_scripts` loads admin assets.
* `admin_notices` renders persistent recovery notices.
* `admin_post_ncsm_save_settings` saves settings.
* `admin_post_ncsm_export_logs` exports logs.
* `admin_post_ncsm_dismiss_notice` dismisses recovery notices.

== Admin Pages ==

* Dashboard: protection status, statistics, and recovery workflow.
* Error Logs: fatal error log table, filters, and CSV export.
* Recovery History: source, action, result, and timestamp.
* Settings: recovery toggles, notifications, fallback theme, retention, maximum attempts.
* Coming Soon: Version 2 feature previews only.

== Settings ==

* Enable Recovery
* Enable Plugin Auto Disable
* Enable Theme Recovery
* Enable Email Notifications
* Fallback Theme Selector
* Log Retention Period
* Maximum Recovery Attempts

== Coming Soon ==

The following features are displayed as UI-only cards and are not implemented in Version 1:

* Automatic Rollback
* Update Sandbox Testing
* Code Snippet Protection
* AI Error Analysis
* Slack Notifications
* Cloud Backups
* Uptime Monitoring
* One Click Restore

== Security ==

Version 1 uses capability checks, nonces, sanitization, escaping, WordPress database APIs, and prepared SQL for dynamic values. It performs no tracking, no hidden data collection, no remote code execution, and no unsafe file rewriting.

== Installation ==

1. Upload the `naveencodes-safe-mode` folder to `/wp-content/plugins/`.
2. Activate the plugin from the WordPress Plugins screen.
3. Go to Safe Mode > Settings and choose a fallback theme.

== Frequently Asked Questions ==

= Does this plugin fix broken PHP code? =

No. It only detects fatal errors, disables faulty plugins or switches broken themes, logs what happened, and notifies administrators.

= Can it recover from every crash? =

No recovery plugin can guarantee recovery from all fatal errors. WordPress must load NaveenCodes Safe Mode before the crash occurs so its shutdown handler can run.

= Does Version 1 include rollback or AI analysis? =

No. Those appear only in the Coming Soon section.

== Screenshots ==

1. Admin notice shown after automatic recovery — confirms what failed and what action was taken.
2. Error Logs — filterable table of every fatal error with source, file, line, and recovery status.
3. Recovery History — chronological record of every recovery action and its outcome.
4. Settings — toggle recovery, auto-disable, theme fallback, email notifications, and retention controls.

== Changelog ==

= 1.0.0 =

* Initial Version 1 release.
* Fatal error detection.
* Plugin auto-disable recovery.
* Theme fallback recovery.
* Recovery queue and attempt limits.
* Custom error logs and recovery history tables.
* Admin dashboard, logs, history, settings, notices, email notifications, and Coming Soon UI.
