Title: Faultline – Error Log Assistant Author: Daniel Chase Published: September 27, 2026 Last modified: October 3, 2026 --- Search plugins ![](https://ps.w.org/faultline-error-log-assistant/assets/banner-772x250.png?rev =3724064) ![](https://ps.w.org/faultline-error-log-assistant/assets/icon-256x256.png?rev=3716098) # Faultline – Error Log Assistant By [Daniel Chase](https://profiles.wordpress.org/riseofweb/) [Download](https://downloads.wordpress.org/plugin/faultline-error-log-assistant.1.2.zip) * [Details](https://vec.wordpress.org/plugins/faultline-error-log-assistant/#description) * [Reviews](https://vec.wordpress.org/plugins/faultline-error-log-assistant/#reviews) * [Installation](https://vec.wordpress.org/plugins/faultline-error-log-assistant/#installation) * [Development](https://vec.wordpress.org/plugins/faultline-error-log-assistant/#developers) [Support](https://wordpress.org/support/plugin/faultline-error-log-assistant/) ## Description **Faultline turns your WordPress error log into answers: what broke, which plugin or theme caused it, and what to do next.** If you have ever turned on `WP_DEBUG`, found an error in the log, and had no idea which plugin caused it or what to do about it, this plugin is for you. #### Find the cause * **Caused by** – every error is matched to the plugin or theme behind it, with a link to that plugin’s WordPress.org support forum. * **Source code** – open the file at the exact line that failed, highlighted. * **Draft forum post** – a ready-to-post support request with the error and your site details filled in, and private details removed. * **Ask AI** – open a copy of the error, private details removed, in Claude, ChatGPT or Perplexity. See “External services” below. #### Know when something breaks * **Fatal error alerts** – a banner in your dashboard, an email, or both, as soon as a fatal error happens. The alert says where it happened: the front end, the admin, a scheduled task, WP-CLI or an AJAX call, and on which page. * **Public access check** – debug.log often sits where anyone can download it, and it contains server paths and plugin details. Faultline tests this the way a stranger would. If your log is exposed, one click moves it to a private file name that bots cannot guess, keeping every entry, and you get the blocking rule for your web server (Apache, LiteSpeed, nginx or IIS). #### Keep the log readable * **Stop routine messages being written** – notices, deprecation warnings and coding- standard suggestions never reach the log, so there is nothing to clean up later. Other debugging tools still see every error. An optional setting loads Faultline before your other plugins, so the notices they raise while starting up are caught too. * **Ignore patterns** – hide one chatty message without hiding its whole category. A live preview shows what will match before you save. * **Automatic cleanup** – remove noise, delete old entries and cap the file size, so a runaway error never fills your disk. * **Fatal errors are always logged.** They cannot be switched off. #### Private details stay private Ask AI links and forum drafts replace server paths, your domain, the database table prefix, email addresses and IP addresses with placeholders before the text leaves your browser. Nothing is sent automatically: you always see the text first. #### Guided setup Setup takes a few minutes, one short screen at a time: * **Previous logs** – finds PHP error logs your site was already writing (such as `error_log` or `php_error.log`) and copies their recent entries into the new log. The original files are only read, never changed. * **Turn on logging** – WordPress needs three settings in `wp-config.php` (`WP_DEBUG`,` WP_DEBUG_LOG` and `WP_DEBUG_DISPLAY`) to log errors without showing them to visitors. Setup checks all three and can make the change for you, with a backup first and a one-click restore. * **Reduce noise** and **Alerts** – sensible defaults, already selected. * **Done** – confirms that logging works and that your log cannot be downloaded from the web. Nothing is removed from an existing log until you finish or skip setup. You can run it again from the Status tab. #### What Faultline will never do * **Write to `.htaccess`.** One bad rule there can take the whole site down, so you get the rule to add yourself. * **Change `wp-config.php` without asking.** It adds the lines that are missing. It changes an existing line in only two cases, each confirmed by you: correcting a single wrong `true`/`false` value, and giving the log a private file name. If a setting is defined more than once, it explains the problem instead of guessing. A backup is taken before every change. * **Hide a fatal error.** Fatal errors, parse errors and uncaught exceptions are always logged. #### External services Faultline can show “Ask AI” links next to each log entry. Links to Claude and ChatGPT are shown by default. Choose which links appear, or turn them all off, under Settings > Troubleshooting links. When you click one of these links, your browser opens that service’s website in a new tab, with a copy of the log entry in the page’s URL. **Faultline itself sends nothing to these services.** There is no server-side request, and nothing is sent until you click a link. Before the link is built, your browser removes server paths, your domain, the table prefix, email addresses and IP addresses from the entry. This is a best-effort pattern match and cannot catch every sensitive detail, such as an order ID or a customer name inside an error message. The services these links can point to: * **Claude** (Anthropic) – [Terms of Service](https://www.anthropic.com/legal/consumer-terms), [Privacy Policy](https://www.anthropic.com/legal/privacy) * **ChatGPT** (OpenAI) – [Terms of Use](https://openai.com/policies/terms-of-use), [Privacy Policy](https://openai.com/policies/privacy-policy) * **Perplexity** – [Terms of Service](https://www.perplexity.ai/hub/legal/terms-of-service), [Privacy Policy](https://www.perplexity.ai/hub/legal/privacy-policy) No service is contacted unless you click its link. ## Screenshots [⌊The Log tab: each entry with its severity, the plugin that caused it, and actions for source code, reporting, Ask AI, copy, ignore and delete.⌉⌊The Log tab: each entry with its severity, the plugin that caused it, and actions for source code, reporting, Ask AI, copy, ignore and delete.⌉[ The Log tab: each entry with its severity, the plugin that caused it, and actions for source code, reporting, Ask AI, copy, ignore and delete. [⌊Setup, at the Reduce noise step, naming the plugins that load before Faultline.⌉⌊ Setup, at the Reduce noise step, naming the plugins that load before Faultline.⌉[ Setup, at the Reduce noise step, naming the plugins that load before Faultline. [⌊The Status tab: log actions and a check of your debug settings.⌉⌊The Status tab: log actions and a check of your debug settings.⌉[ The Status tab: log actions and a check of your debug settings. [⌊The Settings tab, where you choose which types of message stay out of the log.⌉⌊ The Settings tab, where you choose which types of message stay out of the log.⌉[ The Settings tab, where you choose which types of message stay out of the log. [⌊A fatal error caught as it happens: the alert banner, the file that caused it ( here a must-use plugin) and where the request came from.⌉⌊A fatal error caught as it happens: the alert banner, the file that caused it (here a must-use plugin) and where the request came from.⌉[ A fatal error caught as it happens: the alert banner, the file that caused it (here a must-use plugin) and where the request came from. ## Installation 1. In your WordPress admin, go to **Plugins > Add New Plugin**, search for “Faultline” and install it. Or upload the `faultline-error-log-assistant` folder to `/wp-content/ plugins/`. 2. Activate the plugin on the **Plugins** screen. 3. Go to **Tools > Faultline** and follow Setup. It copies any previous PHP error logs, turns on logging (it can edit `wp-config.php` for you, with a backup) and checks that the log cannot be downloaded from the web. 4. After Setup, the same menu item opens the Log tab. Setup can be run again from the Status tab. ## FAQ ### How do I view my WordPress error log? Activate Faultline and go to **Tools > Faultline**. If logging is off, Setup turns it on for you. The Log tab then shows every entry with its severity, the plugin or theme that caused it, and a link to the source code. ### Which plugin is causing this PHP error? Each entry on the Log tab has a “Caused by” label naming the plugin or theme, with a link to that plugin’s WordPress.org support forum. “Draft forum post” writes a support request with the error and your site details filled in. ### How do I turn on WP_DEBUG safely? Use Setup. Three settings have to be right together: `WP_DEBUG`, `WP_DEBUG_LOG` and `WP_DEBUG_DISPLAY`. Get one wrong and either nothing is logged or PHP errors are shown to your visitors. Faultline checks all three and can write the correct lines to `wp-config.php` for you, with a backup first, or give you the lines to paste in yourself. ### How do I stop WordPress from filling up debug.log with notices? Under Settings, tick the types to suppress: notices, deprecation warnings, coding- standard suggestions and, if you choose, warnings. Suppressed messages are never written, so there is nothing to clean up. ### Is my debug.log file publicly accessible to anyone on the internet? It may be. debug.log usually sits in a folder your web server serves, and it contains server paths and stack traces. Faultline requests your log over the web the way a stranger would and tells you whether it could be read. Setup runs this check at the end, and you can repeat it on the Status tab. If the log can be read, a warning shows on every admin screen until it is fixed. There are two fixes: move the log to a private file name that bots cannot guess ( one click, works on any server, keeps every entry), or add a blocking rule for Apache, LiteSpeed, nginx or IIS. On nginx only your host can usually add the rule, so Faultline writes the message to send them. ### I used to have a PHP error log from my host. Will I lose it? No. Setup looks for the PHP error logs your site was writing before, such as the` error_log` files hosting control panels create, and offers to copy their recent entries into the new log. The original files are only read, never edited, moved or deleted. Automatic cleanup also waits until you finish or skip Setup. ### Does this replace my existing log viewer plugin? It can. Faultline shows every log entry with its severity, the plugin or theme that caused it and the source code, alerts you to fatal errors, and keeps routine notices out of `debug.log`. ### What makes this different from other WordPress debug log plugins? Faultline is built for acting on errors, not only reading them. It names the plugin or theme behind each error, opens the line of code that failed, drafts a support request, and links to AI help with private details removed. It can also stop routine notices and deprecation warnings being written in the first place. All of this is free. ### Will this plugin ever show PHP errors to my site visitors? No. Faultline only ever keeps messages out of the log. It never changes PHP’s error reporting level and never turns on `WP_DEBUG_DISPLAY`, the setting that prints errors on screen. Setup sets `WP_DEBUG_DISPLAY` to false. ### Can it guarantee it loads before every other plugin? Not completely. With “Load Faultline first” turned on in Settings, Faultline moves itself ahead of your other plugins and keeps that position when plugins are activated or deactivated. It cannot load before must-use plugins or WordPress itself. The setting is off by default because it changes your site’s plugin order, which should be your choice. The Status tab shows the actual position. ### What happens to wp-config.php if I deactivate or delete the plugin? When you deactivate, Faultline asks whether to undo its `wp-config.php` changes first. Deleting the plugin removes its settings and stored data. It does not touch` wp-config.php` or your log file. ### Does this work on WordPress multisite? Yes, site by site. When the plugin is network-activated, the “Load Faultline first” setting does nothing, because WordPress stores network-wide plugins differently. ### Will suppressing notices hide bugs from me? It hides the types of message you choose, and nothing else. Fatal errors, parse errors and uncaught exceptions are always logged. Warnings are logged unless you turn them off. Notices, deprecation warnings and coding-standard suggestions are suppressed by default because they are rarely something you can act on in someone else’s plugin. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Faultline – Error Log Assistant” is open source software. The following people have contributed to this plugin. Contributors * [ Daniel Chase ](https://profiles.wordpress.org/riseofweb/) [Translate “Faultline – Error Log Assistant” into your language.](https://translate.wordpress.org/projects/wp-plugins/faultline-error-log-assistant) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/faultline-error-log-assistant/), check out the [SVN repository](https://plugins.svn.wordpress.org/faultline-error-log-assistant/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/faultline-error-log-assistant/) by [RSS](https://plugins.trac.wordpress.org/log/faultline-error-log-assistant/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.2 – 2026-10-03 * Log tab hides entries of types you now suppress, with links to show or delete them. * Site Health no longer warns about a public log file once Faultline has confirmed the log cannot be reached. * New Faultline box on the Tools screen. * Setup shows the value each logging setting should have. * Shorter, plainer wording throughout. #### 1.1 – 2026-09-29 * Setup is now a step-by-step wizard, and can copy in the PHP error logs your site already had. * One-click fix for a log that can be downloaded from the web, plus server rules for Apache, LiteSpeed, nginx and IIS. * Automatic cleanup waits until setup is finished or skipped. * Log entries show WordPress formatting (bold, code, links) instead of raw HTML tags. * Status tab trimmed to live facts. * A custom WP_DEBUG_LOG path is no longer reported as wrong. * Faultline actions no longer fail when a theme or plugin prints PHP warnings on screen. * Faultline icon in the page heading and Tools menu. #### 1.0 – 2026-09-27 * Initial release. ## Meta * Version **1.2** * Last updated **3 hours ago** * Active installations **Fewer than 10** * WordPress version ** 5.8 or higher ** * Tested up to **7.1.2** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/faultline-error-log-assistant/) * Tags * [debug](https://vec.wordpress.org/plugins/tags/debug/)[error log](https://vec.wordpress.org/plugins/tags/error-log/) [php errors](https://vec.wordpress.org/plugins/tags/php-errors/)[troubleshooting](https://vec.wordpress.org/plugins/tags/troubleshooting/) [WP_DEBUG](https://vec.wordpress.org/plugins/tags/wp_debug/) * [Advanced View](https://vec.wordpress.org/plugins/faultline-error-log-assistant/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/faultline-error-log-assistant/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/faultline-error-log-assistant/reviews/) ## Contributors * [ Daniel Chase ](https://profiles.wordpress.org/riseofweb/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/faultline-error-log-assistant/)