Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3702287,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3702287,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3702287,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3702287,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3702287,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3702287,"resolution":"1","location":"assets","locale":"","width":1280,"height":800},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3702287,"resolution":"2","location":"assets","locale":"","width":1280,"height":800},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3702287,"resolution":"3","location":"assets","locale":"","width":1280,"height":800},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3702287,"resolution":"4","location":"assets","locale":"","width":1280,"height":800},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3702287,"resolution":"5","location":"assets","locale":"","width":1280,"height":800},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3702287,"resolution":"6","location":"assets","locale":"","width":1280,"height":800}},"screenshots":{"1":"Issues list: every failure source in one place, grouped, with the likely component.","2":"Issue detail: plain-English explanation, what changed before it started, occurrences and stack trace.","3":"Timeline: errors and changes on one axis.","4":"Cron health: next run, overdue flags, durations and Run now.","5":"Dashboard widget with the 7-day sparkline.","6":"Settings: capture sources, early loader, notifications and privacy."}},"plugin_section":[262246],"plugin_tags":[4567,94,267,14925,5603],"plugin_category":[41,54,59],"plugin_contributors":[191403],"plugin_business_model":[],"class_list":["post-367789","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-cron","plugin_tags-debug","plugin_tags-email","plugin_tags-error-log","plugin_tags-monitoring","plugin_category-communication","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-emtiazzahid","plugin_committers-emtiazzahid"],"banners":{"banner":"https:\/\/ps.w.org\/faultwright\/assets\/banner-772x250.png?rev=3702287","banner_2x":"https:\/\/ps.w.org\/faultwright\/assets\/banner-1544x500.png?rev=3702287","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/faultwright\/assets\/icon.svg?rev=3702287","icon":"https:\/\/ps.w.org\/faultwright\/assets\/icon.svg?rev=3702287","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/faultwright\/assets\/screenshot-1.png?rev=3702287","caption":"Issues list: every failure source in one place, grouped, with the likely component."},{"src":"https:\/\/ps.w.org\/faultwright\/assets\/screenshot-2.png?rev=3702287","caption":"Issue detail: plain-English explanation, what changed before it started, occurrences and stack trace."},{"src":"https:\/\/ps.w.org\/faultwright\/assets\/screenshot-3.png?rev=3702287","caption":"Timeline: errors and changes on one axis."},{"src":"https:\/\/ps.w.org\/faultwright\/assets\/screenshot-4.png?rev=3702287","caption":"Cron health: next run, overdue flags, durations and Run now."},{"src":"https:\/\/ps.w.org\/faultwright\/assets\/screenshot-5.png?rev=3702287","caption":"Dashboard widget with the 7-day sparkline."},{"src":"https:\/\/ps.w.org\/faultwright\/assets\/screenshot-6.png?rev=3702287","caption":"Settings: capture sources, early loader, notifications and privacy."}],"raw_content":"\n
\"The site was fine yesterday.\" Faultwright shows you what broke, when it started, which plugin is probably responsible, and what to do about it. No external account, no developer required.<\/p>\n\n
Faultwright keeps a change log: plugin and theme installs, updates, activations, deletions, theme switches, WordPress and PHP version changes, permalink and URL changes. Every issue shows the changes in the 48 hours before its first occurrence, ranked by likelihood.<\/p>\n\n
Over forty built-in explanations cover the errors people actually hit: memory exhausted, maximum execution time, undefined function, cannot redeclare, headers already sent, SMTP authentication, cURL timeouts, mixed content, \"$ is not defined\", chunk load errors and more. Each one says what it means, the likely cause, what to try, and when to contact a developer or your host.<\/p>\n\n
For anything else, an optional bring-your-own-key Explain with AI<\/strong> button sends the error details to OpenAI, Anthropic, Google Gemini or any OpenAI-compatible endpoint (Ollama, Groq, OpenRouter). Nothing is ever sent automatically.<\/p>\n\n Faultwright runs entirely on your own server. It has no telemetry, no account, no licence check and no update server of its own. The only time anything is sent to a third party is the optional \"Explain with AI\" feature described below.<\/p>\n\n Some errors have no built-in explanation. For those, an administrator can turn on \"Explain with AI\" under Faultwright \u2192 Settings \u2192 Explanations, paste their own API key, pick a provider, and then press \"Explain with AI\" followed by \"Send\" on an individual issue. Nothing is sent automatically, on a schedule, or without that second click. Before sending, the screen shows which provider and model will be used and a rough token count.<\/p>\n\n On each click, Faultwright sends one request containing:<\/p>\n\n It does not send your site URL, page URLs, visitor roles, IP addresses, user accounts, email addresses, form data or database contents. The provider's reply is stored in your own database with the issue and is deleted with it. You can adjust or strip the prompt with the The request goes only to the provider you selected:<\/p>\n\n Your API key is stored encrypted in the WordPress options table using your site's authentication salts, is never displayed again beyond its last four characters, and is removed when you clear it or uninstall the plugin.<\/p>\n\n Yes. Faultwright never reads or changes PHP's error-reporting level, so it cannot tell whether a call was wrapped in @. Warnings are grouped and counted, so a silenced call that fails repeatedly shows up as one group. Notices and deprecations are off by default and can be enabled in Settings.<\/p><\/dd>\n No. When nothing goes wrong, the PHP handler costs well under a millisecond and no database queries run on the front end. The JavaScript collector is 1.4 KB and only talks to the server when an error happens. Sampling lets you record a fraction of front-end visitors.<\/p><\/dd>\n No. Faultwright captures errors directly. If WP_DEBUG_LOG is on, new lines in debug.log are imported as well and de-duplicated.<\/p><\/dd>\n No. Nothing leaves your site unless you click \"Explain with AI\" with your own key configured. There is no telemetry.<\/p><\/dd>\n A tiny file copied into wp-content\/mu-plugins that loads Faultwright before every other plugin, so a fatal error raised while another plugin starts up is still captured. You can remove it from Settings \u2192 Capture at any time; uninstalling deletes it.<\/p><\/dd>\n It explains them and points at the most likely culprit with the change history. Rolling a plugin back or contacting the author remains a manual step.<\/p><\/dd>\n Error records store the visitor's role, never a user ID, email address or IP address. IP addresses are hashed (\/24) for rate limiting only and expire after one minute. Query strings are stripped from recorded URLs by default. Failed-email records keep the subject line and, optionally, the recipient domain, never the full address. The change log records which logged-in user activated, updated or changed something, so you can see who did what. The plugin adds a suggested paragraph to Settings \u2192 Privacy \u2192 Policy Guide.<\/p><\/dd>\nEverything else<\/h4>\n\n
\n
wp faultwright issues list<\/code>, wp faultwright issues show <id><\/code>, wp faultwright cron check<\/code>, wp faultwright changes list<\/code>, wp faultwright prune<\/code>, wp faultwright test-error<\/code>, wp faultwright digest<\/code>.<\/li>\nDeveloper hooks<\/h4>\n\n
faultwright_ignore_error, `faultwright_js_noise_patterns`, `faultwright_explanations`, `faultwright_severity`, `faultwright_event_recorded`, `faultwright_notification_channels`, `faultwright_capability`, `faultwright_ai_prompt`, `faultwright_retention_days`, `faultwright_mail_activity_count`.\n<\/code><\/pre>\n\nExternal services<\/h3>\n\n
Explain with AI (optional, off by default)<\/h4>\n\n
\n
faultwright_ai_prompt<\/code> filter.<\/p>\n\n\n
Everything else stays on your site<\/h4>\n\n
\n
\n
faultwright<\/code> folder to \/wp-content\/plugins\/<\/code> or install it from the Plugins screen.<\/li>\n\n
Does it record warnings that were silenced with the @ operator?<\/h3><\/dt>\n
Does it slow my site down?<\/h3><\/dt>\n
Do I need WP_DEBUG on?<\/h3><\/dt>\n
Does it send data anywhere?<\/h3><\/dt>\n
What is the early loader file?<\/h3><\/dt>\n
Can it fix errors?<\/h3><\/dt>\n
Is it GDPR friendly?<\/h3><\/dt>\n