Plugin Conflict Detector Documentation and Changelog

Q: My scan or update test fails, or I see a notice that loopback requests are failing. What do I do?

Scans and update tests need your site to send requests to itself. Some hosts and security plugins block this. Ask your host to allow your site to make HTTP requests to itself, and check whether a security or firewall plugin is blocking them.

Q: My scan stopped moving. Why?

The scan runs while the Scans page is open in your browser. If you close the tab or lose your connection, it stops moving. Open the Scans page again, or cancel the scan and start a new one. On slow hosts a scan may also stop after it runs too long.

Q: The scan finished but found no conflicts, and my site still has a problem. What now?

Try an Incremental (Thorough) scan. Quick Scan only tests plugins updated in the last 7 days, so it can miss older problems. Some problems only happen on certain pages, so also check the Error Log for errors on the page where you see the problem.

Q: My Error Log has lots of JavaScript errors. Are these all plugin conflicts?

Not always. Browser extensions, ad scripts, and other outside scripts can cause errors in a visitor's browser. Open the error and look at the file and page URL. If the file comes from an outside domain, it is likely not caused by your plugins.

Q: The Update Checker shows no updates, but WordPress says I have updates. Why?

Reload the Update Checker page. It asks WordPress for a fresh list of updates when its saved list is empty. On a slow connection the page may take a few extra seconds to load.

Q: An automatic update did not install. Did this plugin stop it?

It may have. If Update Pre-Flight is on and the last test of that update returned Conflict, the automatic update is held back. You will see a notice and get an email if Update Blocked alerts are on. Go to the Update Checker and click Re-test after the plugin author releases a fix.

Q: I am not getting any alert emails. How do I fix it?

Go to Conflict Detector > Settings > Notifications. Make sure Email Notifications is checked and your address is in Email Recipients. Click Send Test Email. If the test does not arrive, check your spam folder. If it still does not arrive, your site may have trouble sending email in general, and an SMTP plugin can help.

Q: I see a message that the plugin is incompatible with WooCommerce. What should I do?

Update Plugin Conflict Detector to the latest version. This was fixed in version 1.0.3.

Q: The plugin will not activate. Why?

It needs WooCommerce 8.0 or higher to be installed and active, WordPress 6.4 or higher, and PHP 7.4 or higher. Activate WooCommerce first, then activate this plugin.

Q: Will this plugin slow down my store?

Monitoring is built to add very little time to each page load. Scans and update tests send test requests to your site in the background, one at a time, while your plugins stay active for visitors.

This page shows you how to install Plugin Conflict Detector, set it up, and use each screen to find plugins that clash on your WooCommerce store. It also covers how to test plugin updates before you apply them and what to do when something does not work as expected.

Requirements: WordPress 6.4 or higher, PHP 7.4 or higher, WooCommerce 8.0 or higher must be installed and active. Current version: 1.1.2.0.

Install the plugin

Make sure WooCommerce is installed and active first. The plugin will not run without it.

Download the plugin-conflict-detector.zip file to your computer.
In your WordPress admin, go to Plugins > Add New Plugin.
Click Upload Plugin at the top of the page.
Click Choose File and select the zip file.
Click Install Now.
When the install finishes, click Activate Plugin.
Look for Conflict Detector in the left admin menu, just below Settings.

First-time setup

The plugin starts working as soon as you activate it. It creates its own storage, turns on error monitoring, and shows a Getting Started box on the dashboard.

Go to Conflict Detector > Dashboard. Read the Getting Started box. Error monitoring is already on.
Go to Conflict Detector > Settings and open the Notifications tab.
In Email Recipients, type the email addresses that should get alerts, separated by commas. Leave it empty to use your site admin email.
Click Save Changes.
Click Send Test Email and check your inbox to make sure alerts reach you.
Go to Conflict Detector > Scans. Leave Scan Mode set to Binary Search (Fast) and click Start Scan to run your first scan.
When you are done with the Getting Started box, click the x in its corner to hide it.

Dashboard

Go to Conflict Detector > Dashboard for a quick look at the health of your store.

Conflict Status: Green means no active conflicts. Yellow means more than 10 errors in the last 24 hours. Red means at least one active conflict was found.
Overview: Shows Active Conflicts, Errors (24h), Scans Run, and conflicts Resolved in the last 30 days.
Quick Actions: Buttons that take you to Run Scan, View Conflicts, Error Log, Update Checker, and Settings.
Error Trend (7 Days): A bar chart of how many errors were logged each day this week.
Plugin Health: Lists up to 5 plugins most involved in open conflicts. Lower scores are better. The score grows with how severe and how frequent the conflicts are.
Recent Errors: The 10 newest errors with their type, message, file, and date. Click View all errors to open the full Error Log.
Pending Updates: Shows how many plugin updates are waiting and how many tested Safe, Caution, Conflict, or are Untested. Click Test Updates to open the Update Checker.

Scans screen

Go to Conflict Detector > Scans to run a conflict scan and see past scans.

Scan Mode: Binary Search (Fast) splits your plugins into groups to find the problem quickly. Incremental (Thorough) tests each plugin one at a time. Quick Scan (Recently Updated) only tests plugins updated in the last 7 days.
Start Scan: Starts a scan with the mode you picked. A progress bar shows which test is running.
Cancel Scan: Stops a scan that is running.
Scan History: Lists past scans with the date, type, status, progress, and number of conflicts found. Status can be Pending, Running, Completed, Failed, or Cancelled.

Conflicts screen

Go to Conflict Detector > Conflicts to see each conflict the plugin found.

Severity filter: Show All, Critical, High, Medium, or Low conflicts.
Status filter: Show Active, Resolved, Ignored, or All conflicts.
Conflict table: Lists the severity, Plugin A, Plugin B, the symptom, a confidence score, and when it was last seen.
Conflict Details: Click a conflict to see when it was first detected, when it was last seen, its status, and a Suggested Resolution.
Mark as Resolved: Use this after you fix the problem. The conflict moves to Resolved.
Ignore: Use this for a conflict you do not want to act on. It moves to Ignored and no longer counts as active.

Error Log screen

Go to Conflict Detector > Error Log to see every error the plugin has captured.

Type filter: Show All Types or one type: PHP Fatal, PHP Warning, JS Error, JS Promise Rejection, JS Console Error, Checkout Validation, Checkout Exception, Payment Failure, Gateway Failure, REST API Error, or Add to Cart Failure.
Status filter: Show Active, Dismissed, or All errors.
Error table: Lists the type, message, file, page URL, and date. The list shows 25 errors per page. Use Previous and Next to move between pages.
Error Details: Click an error to see its level, full message, file, line, page URL, date, the plugins that were active at the time, and a stack trace when one is available.
Dismiss: Hides an error you have already handled. It moves to Dismissed.
Export CSV: Downloads your errors as a spreadsheet file you can share with a developer.

Update Checker screen

Go to Conflict Detector > Update Checker to test plugin updates before you install them. You can also click Test Before Update next to a plugin on your Plugins page.

Available Plugin Updates: Lists each plugin with an update waiting, with its Current and Available version.
Test Update: Tests the new version of one plugin. After a test, the button changes to Re-test.
Test All Updates: Tests every waiting update, one after another.
Safety Verdict: Safe means no issues were found. Caution means warnings or changes were found, so review before you update. Conflict means the new version caused fatal errors, so do not update. Unknown means the test could not finish. Not tested means it has not been checked yet.

Settings: General tab

Go to Conflict Detector > Settings and click the General tab. Click Save Changes after you change anything.

Passive Monitoring: Enable passive error monitoring. Finds PHP and JavaScript errors as they happen. On by default.
Update Pre-Flight: Enable update pre-flight checks. Tests plugin updates for conflicts before you apply them. When on, an automatic update is held back if its last test result was Conflict. On by default.

Settings: Monitoring tab

These settings control which errors passive monitoring records.

PHP Errors: Capture PHP errors and warnings. Logs fatal errors, warnings, and notices along with which plugins were active. On by default.
JavaScript Errors: Capture JavaScript errors. Tracks errors in your visitors' browsers on the front of your site. On by default.
WooCommerce Endpoints: Monitor WooCommerce endpoints. Tracks errors on the cart, checkout, and my-account pages. On by default.
Checkout Flow: Monitor checkout flow. Finds errors during the checkout process. On by default.

Settings: Scanning tab

These settings control how conflict scans behave.

Settings: Notifications tab

These settings control which emails the plugin sends and who gets them.

Email Notifications: Enable email notifications. Turns all alert emails on or off. On by default.
Critical Alerts: Send alert on critical conflicts. Emails you right away when a critical or high severity conflict, or a fatal PHP error, is found. On by default.
Scan Complete: Send notification when scan completes. Emails you a summary after each scan. Off by default.
Update Blocked: Send alert when an auto-update is blocked. Emails you when an automatic plugin update is held back because of a conflict. On by default.
Weekly Digest: Send weekly summary digest. Emails you a weekly summary of errors, new conflicts, active conflicts, and scans. On by default.
Email Recipients: Email addresses to send alerts to, separated by commas. Leave empty to use your site admin email.
Send Test Email: Sends a test message so you can confirm alerts reach your inbox.

Reading your results day to day

Start on the Dashboard. If Conflict Status is green, there is nothing to do. If it is yellow or red, open the Conflicts screen or the Error Log.

The plugin records PHP fatal errors, warnings, and notices. It records JavaScript errors, unhandled promise rejections, and console errors from your visitors' browsers. On your store it also watches for checkout validation errors, checkout exceptions, payment failures, payment gateway failures, REST API errors, and add to cart failures.

Each error is saved with the plugins that were active when it happened. Once a day, the plugin looks for patterns in these errors and lists likely conflicts on the Conflicts screen with a severity and a confidence score.

Severity tells you how urgent a conflict is. Fatal PHP errors, checkout exceptions, and payment failures are Critical. Checkout validation errors, gateway failures, and REST API errors are High. Other errors become Medium or High as they repeat more often.

Alert emails have a subject that starts with your site name in brackets. Examples are Critical PHP Error Detected, Conflict Detected, Scan Complete, Auto-Update Blocked, and Weekly Conflict Detector Digest. Each email has a link that opens the right screen in your admin.

You may also see notices at the top of your admin pages. One tells you when an automatic update was blocked and links to the Update Checker. Another warns you when your site cannot reach itself, which stops scans and update tests from working.

When you fix a conflict, mark it as Resolved. When you have handled an error, dismiss it. This keeps your dashboard counts accurate.

Running a conflict scan

A scan tests your site with different groups of plugins turned off, one test at a time, and compares each result to a normal page load. Your plugins stay active for your visitors the whole time.

Go to Conflict Detector > Scans.
Pick a Scan Mode. Use Binary Search (Fast) for most problems. Use Incremental (Thorough) if the fast scan finds nothing but the problem is still there. Use Quick Scan (Recently Updated) if trouble started after a recent update.
Click Start Scan and confirm.
Keep the Scans page open while the scan runs. The progress bar shows which test is running.
When the scan finishes, the page reloads. Check Scan History for the result.
If conflicts were found, go to Conflict Detector > Conflicts to see the plugins involved and the suggested fix.
To stop a scan early, click Cancel Scan.

Deactivating and uninstalling

When you deactivate the plugin, monitoring and scanning stop and scheduled tasks are cleared. Your settings, errors, scans, and conflicts are kept in case you turn it back on.

When you delete the plugin from the Plugins page, it removes all of its data. This includes its settings, its saved scans, conflicts, and errors, and any temporary data it stored. This cannot be undone, so export your Error Log first if you want to keep a copy.

Troubleshooting

My scan or update test fails, or I see a notice that loopback requests are failing. What do I do?

My scan stopped moving. Why?

The scan finished but found no conflicts, and my site still has a problem. What now?

My Error Log has lots of JavaScript errors. Are these all plugin conflicts?

The Update Checker shows no updates, but WordPress says I have updates. Why?

An automatic update did not install. Did this plugin stop it?

I am not getting any alert emails. How do I fix it?

I see a message that the plugin is incompatible with WooCommerce. What should I do?

The plugin will not activate. Why?

Will this plugin slow down my store?

Does the plugin work with caching plugins?

I fixed a problem. How do I clear it from the dashboard?

Changelog

Version 1.1.2.0 September 13, 2026

Fixed a site error that could happen when another plugin from the same developer was also active.
Fixed automatic update checks so new versions of this plugin are offered correctly.

Version 1.1.1 June 15, 2026

Improved stability so a missing update component no longer causes a site error.

Version 1.1.0 June 13, 2026

Changed: Simplified the admin menu and removed promotional notices.

Version 1.0.4 June 11, 2026

Improved: Security improvements.

Version 1.0.3 February 27, 2026

Fixed the incompatible with WooCommerce warning on the Plugins screen.
Fixed the Update Checker showing zero updates when updates were waiting.
Changed the Conflict Detector menu to sit below Settings instead of near WooCommerce Marketing.
Added support for the WooCommerce block checkout and the new product editor.
Improved update testing on hosts that limit some server functions.

Version 1.0.2 February 13, 2026

Added support for WooCommerce High-Performance Order Storage.
Fixed detection of WooCommerce when it is network activated on multisite.
Improved compatibility with WordPress 6.9 and WooCommerce 10.5.
Added a translation template so the plugin can be translated.

Version 1.0.1 February 13, 2026

Improved: Security improvements.

Version 1.0.0 February 12, 2026

Added passive error monitoring for PHP, JavaScript, and WooCommerce cart, checkout, and payment errors.
Added conflict scans with Binary Search, Incremental, and Quick Scan modes.
Added the Update Checker with Safe, Caution, Conflict, and Unknown verdicts.
Added the dashboard, Conflicts screen, and Error Log with CSV export.
Added email alerts, a weekly digest, and a Getting Started guide.

Plugin Conflict Detector documentation