=== Dprime Error Catcher ===
Contributors: dprimesolutions
Tags: debugging, errors, fatal, php, log
Requires at least: 6.4
Tested up to: 7.1
Requires PHP: 8.2
Stable tag: 1.3.1
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Catches PHP fatal errors and logs them to a viewable file. Install before testing risky plugin uploads or code changes.

== Description ==

When PHP fatals on a production WordPress site, you usually get a blank white page with no information about what failed. This plugin hooks into PHP shutdown, captures fatal errors, writes them to a log file, and shows a red banner across wp-admin so you notice straight away.

Use it when:

* Uploading or activating untested plugins
* Updating PHP versions
* Debugging a reported "site went blank" issue
* Investigating any plugin or theme code change

Not intended for long-term production use. Install when debugging, remove when done.

Main features:

* Log viewer tab showing the most recent 200 error entries
* CSS classes tab listing all overridable classes for custom styling
* Help tab with plain-language guidance on when and how to use the plugin
* Clear log button to wipe the file when debugging is complete
* Nests under the Dprime parent menu when Dprime Core is installed

== Installation ==

1. Upload the dprime-error-catcher folder to /wp-content/plugins/
2. Activate the plugin from the Plugins screen
3. Reproduce the issue you are investigating
4. Go to Dprime > Error Catcher and check the Log tab

== Frequently Asked Questions ==

= Does this plugin need Dprime Core? =

No. Error Catcher works fully on its own. If Dprime Core is installed, Error Catcher nests under the Dprime parent menu automatically.

= What types of errors are captured? =

Fatal errors only. These are errors that stop the page loading completely. Warnings and notices are not captured. Use WP_DEBUG_LOG in wp-config.php for those.

= Where is the log file stored? =

At wp-content/dprime-error.log. The file is outside the plugins folder so it survives deactivation.

= Will the plugin slow down my site? =

No. The shutdown function only does work when a fatal error has already occurred. On a normal request it adds no overhead.

= What happens when I delete the plugin? =

The log file at wp-content/dprime-error.log is deleted automatically when you remove the plugin.

== Screenshots ==

1. The Error Catcher log viewer showing captured PHP fatal errors
2. The Help tab with plain-language guidance
3. The CSS classes tab listing available override classes

== Changelog ==

= 1.3.1 =
* Moved logs outside the public web root when possible, with a protected hashed fallback.
* Added locked writes, size-based rotation, bounded log viewing, and complete cleanup.
* Promoted the verified release to the stable channel.

= 1.2.2 =
* Fixed help tab: removed server file path and corrected uninstall message

= 1.2.1 =
* Help tab moved to last position
* Footer: Dprime Solutions now links to dprime.au directly

= 1.2.0 =
* Refactored to class-based structure
* Added CSS classes tab for developer overrides
* Added company footer with plugin page link
* Updated help tab for non-technical users
* Tabs now switch client-side
* Fixed header logo SVG
* Added uninstall.php

= 1.1.0 =
* Added Help tab with full usage documentation
* Added includes/help.php as a separate include
* Added override CSS class documentation

= 1.0.2 =
* Full Dprime design system styling
* Log viewer and Help tabs
* Clear log action
* Canonical menu pattern

= 1.0.1 =
* Initial release

== Upgrade Notice ==

= 1.2.0 =
Recommended update. Adds a CSS classes tab, client-side tabs, and a footer with plugin links. No settings changes required.
