Title: Privileged Conflict Diagnostics Author: privilegedusa Published: 30.04.2026 Last modified: 30.04.2026 --- Поиск плагинов ![](https://ps.w.org/privileged-conflict-diagnostics/assets/banner-772x250.png?rev =3519888) ![](https://ps.w.org/privileged-conflict-diagnostics/assets/icon-256x256.png?rev =3519888) # Privileged Conflict Diagnostics Автор: [privilegedusa](https://profiles.wordpress.org/brandonrevering/) [Скачать](https://downloads.wordpress.org/plugin/privileged-conflict-diagnostics.1.12.21.zip) * [Детали](https://ru.wordpress.org/plugins/privileged-conflict-diagnostics/#description) * [Отзывы](https://ru.wordpress.org/plugins/privileged-conflict-diagnostics/#reviews) * [Установка](https://ru.wordpress.org/plugins/privileged-conflict-diagnostics/#installation) * [Разработка](https://ru.wordpress.org/plugins/privileged-conflict-diagnostics/#developers) [Поддержка](https://wordpress.org/support/plugin/privileged-conflict-diagnostics/) ## Описание 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. Google Maps Platform terms: https://cloud.google.com/maps-platform/terms Google Privacy Policy: https://policies.google.com/privacy ## Установка 1. Upload the plugin folder to `/wp-content/plugins/`. 2. Activate the plugin through the Plugins screen in WordPress. 3. Visit Tools Privileged Conflict Diagnostics. 4. When troubleshooting a specific page while logged in as an administrator, use the top admin bar action to analyze the current page. ## Часто задаваемые вопросы ### Does this plugin automatically disable plugins? No. Privileged Conflict Diagnostics is diagnostic only. It helps identify likely issues and provides a safer investigation workflow. ### Does Test Mode affect all visitors? No. Test Mode is intended to be session-only for the current admin user. ### Can duplicate libraries always be treated as a true conflict? Not always. Duplicate or overlapping libraries are heuristic findings that may indicate a likely source of problems, but they are not guaranteed to be the direct cause. ## Отзывы Нет отзывов об этом плагине. ## Участники и разработчики «Privileged Conflict Diagnostics» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники: Участники * [ privilegedusa ](https://profiles.wordpress.org/brandonrevering/) [Перевести «Privileged Conflict Diagnostics» на ваш язык.](https://translate.wordpress.org/projects/wp-plugins/privileged-conflict-diagnostics) ### Заинтересованы в разработке? [Посмотрите код](https://plugins.trac.wordpress.org/browser/privileged-conflict-diagnostics/), проверьте [SVN репозиторий](https://plugins.svn.wordpress.org/privileged-conflict-diagnostics/), или подпишитесь на [журнал разработки](https://plugins.trac.wordpress.org/log/privileged-conflict-diagnostics/) по [RSS](https://plugins.trac.wordpress.org/log/privileged-conflict-diagnostics/?limit=100&mode=stop_on_copy&format=rss). ## Журнал изменений #### 1.12.21 * Renamed the public plugin title to Privileged Conflict Diagnostics for directory compatibility. * Updated text domain and internal admin/menu slugs to privileged-conflict-diagnostics. * Refreshed readme metadata, tags, short description, and Tested up to value. * Removed the discouraged load_plugin_textdomain() call for WordPress.org-hosted distribution. * Improved request sanitization and added translator comments for placeholder strings. #### 1.12.17 * Added activation defaults so analyzer options are initialized with non-autoloaded storage. * Hardened Test Mode selection saving so only valid active plugin candidates are stored. * Fixed Theme tab persistence through scan and Test Mode postbacks. * Expanded uninstall cleanup to remove per-user Test Mode metadata. * Polished directory-readiness readme sections, screenshots list, and upgrade notice. #### 1.12.16 * Added deeper plugin-specific settings hints based on detected libraries, contested hooks, and overlapping feature areas. * Improved plugin action plans so they point toward more exact modules such as CAPTCHA ownership, payment buttons, script output, builder widgets, and analytics injection. #### 1.12.15 * Added before/after hook-pressure compare output with per-hook callback deltas. * Strengthened theme-aware ranking for theme + builder, eCommerce, optimization, and analytics overlaps. #### 1.12.14 * Added smarter known conflict signature scoring for SEO, optimization, page builder, CAPTCHA, payment, and maps-style overlaps. * Expanded plugin-family coverage so more common stacks receive stronger ranking influence and plugin-specific guidance. #### 1.12.13 * Reworked the Theme Conflict Diagnostics tab to match the broader dashboard workflow more closely. * Kept the top summary and theme-specific action plan visible while moving suspect and technical sections into accordions. #### 1.12.12 * Restored the Theme Conflict Diagnostics content to the main workspace shell so it visually matches the other dashboard tabs. * Fixed wrapper alignment and spacing around the theme tab layout. #### 1.12.11 * Repaired broken dashboard wrapper markup that caused Test Mode to render inside the environment scan section. * Restored Action Plans, Technical Findings, and Theme Conflict Diagnostics tab content rendering. #### 1.12.10 * Strengthened compare-aware suspect promotion and demotion so Theme pairs move up more clearly when theme-owned signals remain after plugin retests. * Added before/after theme pressure tracking for duplicate libraries, contested hooks, and theme-linked pairs. * Added compare-aware score deltas to ranked conflict pairs and clearer theme verdict messaging in the dashboard. #### 1.12.6 * Updated the admin bar Analyze This Page icon to use dashicons-analytics. * Tightened icon and text spacing in the admin bar action. * Synced plugin version metadata and readme. #### 1.12.3 * Updated the tab workflow so running a scan keeps you in the active section, highlights that results were refreshed, and better signals when scan data changed. * Updated dashboard buttons to use black by default with lime hover states. * Renamed the admin-bar action to Analyze This Page and switched it to a magnifying- glass icon. #### 1.12.2 * Polished the tabbed dashboard into a lighter WordPress-friendly layout with black action buttons and lime-green accents. * Added icons to key tabs, stat cards, and section headers for clearer scan flow. #### 1.12.0 * Reworked the analyzer dashboard into a tabbed workspace for Overview, Capture& Test, Action Plans, and Technical Findings. * Added a darker styled UI with a black and lime green color scheme for a more distinctive product feel. #### 1.11.0 * Added compare-aware recommendations that interpret retest results and promote or demote suspects based on before and after captures. * Added compare-aware guidance output to Test Mode and the exported text report. #### 1.10.1 * Added plugin-specific conflict rules for known plugin families and known settings locations. * Added Plugin-Specific Action Plans section with stronger next-step guidance. * Folded plugin-specific rules into summary findings, suggested actions, and text export. #### 1.9.1 * Moved before and after compare results into the Test Mode section. * Removed the separate compare section and clarified workflow wording. #### 1.9.0 * Added category-aware conflict action plans for overlapping SEO, optimization, security, CAPTCHA, payment, forms, and maps patterns. * Added stronger rule-based guidance for duplicate Stripe, reCAPTCHA, Google Maps, and Select2 signatures. * Folded category overlap signals into the likely conflict pair ranking and report export. #### 1.8.1 * Fixed a packaging issue that could trigger a fatal error on the analyzer page. * Restored the core plugin files to the expected root structure. * Made How to run a page-specific capture test, Run environment scan, Test Mode, and Summary Findings always expanded. * Kept secondary result sections collapsible. * Kept Before and After Compare directly below Summary Findings. #### 1.7.0 * Added stronger action guidance tied to contested hooks and top suspect pairs. * Added collapsible accordion sections on the analyzer dashboard to reduce page length and clutter. * Improved captured-page troubleshooting instructions with more direct step-by- step actions. #### 1.6.0 * Added hook and filter collision analysis with contested hook reporting. * Folded contested hooks into suspect pair ranking, summary findings, known warnings, and text export. * Added a Hook and Filter Collisions dashboard section with owners, priorities, and callback details. #### 1.5.0 * Added before and after compare mode for repeated captures of the same page. * Stored Test Mode state with each capture so comparisons show what changed. * Added compare summary to the dashboard and report export. #### 1.4.0 * Added frontend page capture support from the top admin bar for logged-in administrators. * Unified the capture action as Analyze This Page for both admin and frontend workflows. * Improved page-specific workflow wording so captured page guidance applies to frontend issues too. #### 1.3.2 * Added clearer post-capture guidance with direct next-step actions and quick links into Test Mode. * Added a camera icon to the admin-bar capture action so it stands out more. * Clarified that capture alone does not prove a page is conflict-free; Test Mode is the validation step. #### 1.3.1 * Made the admin-bar capture button visible on the analyzer screen as well as other admin pages. * Enabled capture submission on the analyzer screen so the button no longer appears missing or inactive there. * Added a small admin-bar helper item to clarify that useful captures should be taken from the broken admin screen. #### 1.3.0 * Added true admin-screen capture workflow using a top admin bar action. * Added exact page-specific troubleshooting steps tied to the captured admin screen URL. * Improved suggested actions so they explain how to use Test Mode step by step. * Added captured page metadata and open-page shortcuts on the dashboard. * Clarified that standard frontend scans are still environment-level, not live page captures. #### 1.2.0 * Added likely conflict pair ranking based on duplicate libraries, AJAX overlaps, REST overlaps, and error signals. * Added a page-specific troubleshooting workflow section with ordered test guidance. * Improved duplicate library owner attribution, including inferred-owner handling for alias or missing-source entries. * Improved report output with conflict pair rankings and troubleshooting steps. #### 1.1.0 * Added confidence-scored duplicate library findings. * Added known conflict warnings for common duplicate library patterns. * Added recent scan history to the dashboard. * Improved exported report detail for duplicate libraries and warnings. #### 1.0.3 * Updated admin sidebar label handling for Privileged Conflict Diagnostics naming. * Improved suggested actions wording in scan results. * Corrected plugin metadata consistency. #### 1.0.2 * Added stronger duplicate library detection using handle, source, owner, and version comparisons. * Improved asset owner attribution. * Updated plugin author metadata to Privileged.Design. * Updated admin Tools label to Privileged Conflict Diagnostics. #### 1.0.1 * Improved REST route and AJAX action analysis. * Expanded report output and scanner summary details. * Improved Test Mode state handling and dashboard reporting. #### 1.0.0 * Initial public plugin foundation release. * Added dashboard, scanner framework, asset scanning foundation, reporting foundation, and Test Mode groundwork. ## Мета * Версия **1.12.21** * Обновление: **6 дней назад** * Активных установок: **Менее 10** * Версия WordPress ** 6.3 или выше ** * Совместим вплоть до: **6.9.4** * Версия PHP ** 7.4 или выше ** * Язык * [English (US)](https://wordpress.org/plugins/privileged-conflict-diagnostics/) * Метки: * [debugging](https://ru.wordpress.org/plugins/tags/debugging/)[developer-tools](https://ru.wordpress.org/plugins/tags/developer-tools/) [plugin conflicts](https://ru.wordpress.org/plugins/tags/plugin-conflicts/)[troubleshooting](https://ru.wordpress.org/plugins/tags/troubleshooting/) * [Дополнительно](https://ru.wordpress.org/plugins/privileged-conflict-diagnostics/advanced/) ## Оценки Пока что нет ни одного отзыва. [Your review](https://wordpress.org/support/plugin/privileged-conflict-diagnostics/reviews/#new-post) [Посмотреть всеотзывы](https://wordpress.org/support/plugin/privileged-conflict-diagnostics/reviews/) ## Участники * [ privilegedusa ](https://profiles.wordpress.org/brandonrevering/) ## Поддержка Есть что сказать? Нужна помощь? [Перейти в форум поддержки](https://wordpress.org/support/plugin/privileged-conflict-diagnostics/)