Clashlens – Conflict Detector

Something on your site breaks. The slider stops moving, the checkout button does nothing, a page turns white. The usual advice is to deactivate every plugin and switch them back on one at a time, which means taking your live site apart while visitors are on it. Clashlens reads the evidence instead. One click scans your active plugins and gives you a severity-rated report: green when things look fine, red when something needs attention, and a named plugin wherever the data supports one. What Clashlens checks Known incompatible plugin pairs. Your active plugins are compared against a curated list of combinations known to clash: two SEO plugins competing over meta tags, two caching plugins writing conflicting output, duplicate SSL redirect handlers causing redirect loops, two page builders fighting over the editor. Each hit names both plugins and explains the problem in one sentence, so you know exactly which one to deactivate. Pairs that are merely redundant rather than harmful are marked as such and never inflate your overall status. Dangerous overrides and jQuery conflicts. Every PHP file of every active plugin is scanned for calls that commonly break other plugins: remove_all_actions, remove_all_filters, deregistering jQuery, or dequeuing core styles. A plugin that deregisters jQuery is one of the most common reasons a slider, lightbox, or form suddenly stops working. Scanning is capped per plugin so it stays fast on large sites. PHP errors grouped by plugin. Clashlens reads your debug.log and attributes fatal errors, warnings and notices to the plugin that produced them, over the last 7 days. A plugin generating 50 or more errors in a single day is flagged critical. Only the tail of the log is read, so even a multi-gigabyte debug.log will not exhaust memory. Hook collisions. Hooks where three or more plugins registered callbacks at the same priority are listed as investigation starting points. Common core lifecycle hooks are excluded because crowding there is completely normal, and this check deliberately never rates your site critical on its own. Who it is for Site owners debugging a broken page, developers taking over an unfamiliar site, agencies auditing client installs before an update, and anyone who has ever lost an afternoon to plugin compatibility troubleshooting. What it will not do Clashlens never deactivates, modifies, or repairs anything. It reports what it finds and leaves every decision to you. It also cannot see JavaScript errors that happen in the visitor's browser, and because the scan runs in the admin area, hooks that plugins register only on front-end requests are invisible to the hook collision check. Both are on the roadmap. Privacy Clashlens sends nothing anywhere. No external requests, no tracking, no analytics. Scan results are stored in your own database and removed when you uninstall the plugin.

1. Upload clashlens to /wp-content/plugins/, or install it from Plugins → Add New.
2. Activate the plugin through the Plugins screen.
3. Go to Settings → Clashlens and click Run Scan.

Results stay stored until you run the next scan, so you can close the page and come back to them.

1.0.0

• Initial release.