About this plugin
Privileged Conflict Diagnostics helps WordPress admins investigate likely plugin and theme conflicts without immediately disabling plugins site-wide.
It is designed for safe production troubleshooting:
– it does not auto-disable plugins for all visitors
– Test Mode only affects the current logged-in admin account
– page capture lets you analyze the exact admin or frontend page where the issue appears
– compare mode helps you see what changed after a targeted retest
Current features include:
– tabbed admin conflict analysis dashboard
– exact page capture from the admin bar
– environment scans for admin or frontend context
– duplicate handle and duplicate library detection
– asset owner attribution heuristics
– hook and filter collision analysis
– theme conflict analysis and theme-aware suspect ranking
– likely conflict pair ranking
– compare-aware before/after guidance
– plugin-specific and category-based action plans
– REST route overlap reporting
– AJAX action overlap reporting
– debug log signal summaries
– session-only Test Mode
– text report export
Privileged Conflict Diagnostics is a diagnostic tool. It does not automatically disable plugins site-wide or make destructive changes to the site.
External Services
Privileged Conflict Diagnostics does not intentionally send data to external services and does not load third-party APIs for its own functionality.
During scans, the plugin inspects scripts and styles that are already registered, enqueued, or present on the current WordPress request so it can identify likely duplicate libraries, duplicated external assets, or conflict patterns. For example, it may recognize a Google Maps asset URL if another active plugin or theme has already enqueued that asset.
The plugin does not contact Google Maps or any other third-party service as part of this detection. Any external request is made by the plugin, theme, or custom code that originally enqueued the asset, not by Privileged Conflict Diagnostics. The detected asset URL, handle, version string, and inferred owner may be stored locally in WordPress options as part of the scan report for the site administrator.
Recognized third-party asset signatures may include Google Maps Platform assets. com/privacy