Is a WordPress plugin breaking your website?\nConflict Guard helps you find the culprit without taking your site offline.\nStop disabling plugins one-by-one and guessing which update caused the problem.\nConflict Guard is a WordPress troubleshooting and plugin conflict detection tool that helps you identify problems involving plugins, PHP errors, JavaScript errors, AJAX failures, REST API issues, WooCommerce checkout problems, and more.\nUse Safe Test Mode to test plugin combinations from your administrator session while visitors continue seeing your normal live website.\n\ud83d\udd0d Find the Plugin Causing the Problem\nConflict Guard scans your active plugins and analyzes your site\u2019s diagnostic information to help identify potential conflicts and stability problems.\nIt can monitor:\nPHP errors and fatal errors\nJavaScript errors\nAJAX failures\nREST API problems\nPlugin-related issues\nWooCommerce compatibility problems\nPlugin update and activation events\nEach plugin can receive a stability score based on detected error activity.<\/p>\n\n
\ud83e\uddea Test Plugin Conflicts Safely\nSafe Test Mode creates a session-based testing environment for your administrator account.\nYou can temporarily disable plugins while testing without changing what normal visitors see.\nThis means you can troubleshoot a live website without deliberately taking the site offline for everyone.\nVisitors: Continue seeing the normal website.\nAdministrator: Can test plugins in the Safe Test Mode session.<\/p>\n\n
\ud83c\udfaf Isolate the Problem Plugin\nNot sure which plugin is responsible?\nConflict Guard includes a smart conflict isolation system that helps narrow down the potential culprit instead of requiring you to manually deactivate every plugin individually.\nThe goal is simple:\nScan \u2192 Test \u2192 Isolate \u2192 Identify \u2192 Fix<\/p>\n\n
\u23ea Roll Back Problematic Plugin Updates\nA plugin update can sometimes introduce compatibility problems.\nConflict Guard provides rollback functionality for WordPress.org-hosted plugins, allowing you to select an available previous version and restore it.\nAutomatic restore points are also created before plugin updates where supported by Conflict Guard.\nFor premium or third-party plugins, automatic WordPress.org version downloads are not available, but Conflict Guard can create restore points before updates.<\/p>\n\n
\ud83d\udea8 Emergency Recovery Mode\nIf a WordPress problem prevents you from accessing the normal WordPress admin area, Conflict Guard provides an Emergency Recovery interface.\nKeep your personal recovery URL available so you can access the recovery tools when the normal dashboard is unavailable.\nRecovery and file-changing actions require appropriate administrator permissions.<\/p>\n\n
\ud83d\udcca Real-Time Error Monitoring\nConflict Guard provides diagnostic information about problems occurring on your website.\nMonitor information such as:\nPHP errors\nFatal errors\nJavaScript conflicts\nAJAX failures\nREST API issues\nMemory usage\nPlugin-related error activity\nUse the information to determine what changed and where to investigate.<\/p>\n\n
\ud83d\uded2 WooCommerce Troubleshooting\nRunning WooCommerce?\nConflict Guard includes dedicated WooCommerce diagnostics for common store problems.\nUse it to investigate:\nCheckout problems\nPayment gateway conflicts\nWooCommerce plugin compatibility\nPlugin-related checkout failures\nWhen your store\u2019s checkout suddenly stops working, finding the responsible plugin quickly can save hours of troubleshooting.<\/p>\n\n
\ud83d\udcc5 Conflict Timeline\nConflict Guard records important plugin events so you can understand what happened before a problem appeared.\nThe timeline can help you investigate:\nPlugin activations\nPlugin deactivations\nPlugin updates\nRollbacks\nDetected errors\nCrashes\nConflict events\nThis makes it easier to answer the question:\n\u201cWhat changed before my website broke?\u201d<\/p>\n\n
\ud83d\udcc8 Plugin Health & Stability\nConflict Guard provides plugin health information to help you identify plugins that may deserve closer investigation.\nDepending on the available diagnostic information, plugins can receive scores related to:\nStability\nSecurity\nUpdate activity\nPerformance impact\nThese scores are intended as troubleshooting indicators, not absolute security or performance guarantees.<\/p>\n\n
\ud83d\udee1\ufe0f Built for Safe Troubleshooting\nConflict Guard is designed to make troubleshooting safer.\nFeatures include:\nSession-based Safe Test Mode\nAdministrator capability checks\nNonce verification\nPrepared database queries\nCached\/background scanning where appropriate\nEmergency recovery tools\nRestore points for supported updates<\/p>\n\n
\ud83d\ude80 How It Works\n1. Install Conflict Guard\nInstall and activate Conflict Guard from the WordPress plugin directory.\n2. Run a Scan\nOpen Conflict Guard in your WordPress admin area and run a diagnostic scan.\n3. Review the Results\nCheck plugin stability information and detected errors.\n4. Test Safely\nUse Safe Test Mode to temporarily disable plugins for your administrator session.\n5. Isolate the Culprit\nNarrow down the plugin or combination of plugins causing the problem.\n6. Fix or Roll Back\nOnce you identify the likely cause, fix the configuration, update the plugin, or roll back a supported WordPress.org plugin version.\n\ud83d\udca1 Common Problems Conflict Guard Can Help Investigate\nConflict Guard can help troubleshoot situations such as:\n\u201cMy WordPress site broke after installing a plugin.\u201d\n\u201cMy website stopped working after a plugin update.\u201d\n\u201cWhich plugin is causing this error?\u201d\n\u201cMy WooCommerce checkout stopped working.\u201d\n\u201cMy payment gateway stopped working.\u201d\n\u201cWordPress is showing a fatal error.\u201d\n\u201cA plugin is causing JavaScript errors.\u201d\n\u201cMy AJAX functionality stopped working.\u201d\n\u201cThe REST API is failing.\u201d\n\u201cI need to test plugins without affecting visitors.\u201d\n\u201cI need to roll back a plugin update.\u201d\n\ud83e\udde9 Compatibility\nConflict Guard is designed to work with:\nWordPress 6.0+\nPHP 8.0+\nWooCommerce\nElementor\nGutenberg\nWordPress Multisite\nShared hosting environments\nCloud hosting environments\nLocal development environments such as Local, XAMPP, WAMP, and MAMP\nActual compatibility can depend on the specific plugins, themes, hosting configuration, PHP version, and WordPress environment.<\/p>\n\n
\ud83c\udd93 Free to Use\nConflict Guard is free to use.\nThere are no locked troubleshooting features and no mandatory premium upgrade.\nIf Conflict Guard saves you time, you can support continued development through the donation option available in the plugin.<\/p>\n\n
\ud83d\udd10 Privacy & Security\nConflict Guard is designed to perform diagnostics locally on your WordPress installation.\nThe plugin uses WordPress security mechanisms including capability checks, nonce verification, and prepared database queries.\nThe plugin does not require an external account or subscription to perform its core troubleshooting functions.<\/p>\n\n
Conflict Guard connects to WordPress.org services only when required for supported rollback operations.\nWordPress.org Plugin API\nWhat it is: The official WordPress.org plugin information API.\nWhat it is used for: Retrieving available previous versions of a WordPress.org-hosted plugin when you request version information for a rollback.\nWhat data is sent: The WordPress.org plugin slug only. No personal data or website content is sent.\nWhen data is sent: Only when you request available versions for a plugin.\nEndpoint: https:\/\/api.wordpress.org\/plugins\/info\/1.0\/{plugin-slug}.json\nService provider: Automattic \/ WordPress.org\nTerms of Service: https:\/\/wordpress.org\/about\/privacy\/\nPrivacy Policy: https:\/\/automattic.com\/privacy\/\nWordPress.org Plugin Downloads\nWhat it is: The official WordPress.org plugin download service.\nWhat it is used for: Downloading the selected previous plugin version when you perform a supported rollback.\nWhat data is sent: The plugin slug and selected version number only.\nWhen data is sent: Only when you perform a rollback.\nEndpoint: https:\/\/downloads.wordpress.org\/plugin\/{slug}.{version}.zip\nService provider: Automattic \/ WordPress.org\nTerms of Service: https:\/\/wordpress.org\/about\/privacy\/\nPrivacy Policy: https:\/\/automattic.com\/privacy\/<\/p>\n\n\n
Install Conflict Guard from the WordPress plugin directory.\nActivate the plugin through the Plugins screen in WordPress.\nOpen Conflict Guard from the WordPress admin menu.\nRun your first scan.\nReview the diagnostic results.\nIf you are investigating a conflict, activate Safe Test Mode and begin testing.<\/p>\n\n\n
No.\nSafe Test Mode is session-based. Plugin changes made during Safe Test Mode affect the administrator\u2019s testing session rather than normal visitors.\nVisitors continue seeing the normal live website.<\/p><\/dd>\n
Conflict Guard provides automatic conflict detection and a conflict isolation system to help narrow down potential causes.\nSome problems can have multiple causes, including themes, hosting configuration, WordPress core, server configuration, or external services. Conflict Guard should therefore be treated as a troubleshooting tool rather than a guarantee of a single root cause.<\/p><\/dd>\n
Yes.\nSafe Test Mode is specifically designed to allow administrators to investigate plugin conflicts without intentionally changing the experience of normal visitors.\nAlways maintain a reliable website backup before performing plugin updates, rollbacks, or other file-changing operations.<\/p><\/dd>\n
Automatic version downloads are supported for plugins hosted on WordPress.org.\nPremium and third-party plugins are not downloaded from WordPress.org by Conflict Guard. Restore points may still be available for supported update workflows.<\/p><\/dd>\n
Yes.\nConflict Guard includes WooCommerce diagnostics for investigating checkout problems, payment gateway conflicts, and plugin compatibility issues.<\/p><\/dd>\n
Yes.\nConflict Guard includes error monitoring and Emergency Recovery functionality designed to help investigate and recover from plugin-related problems.\nThe exact recovery options available depend on the state of your WordPress installation and the permissions available to your administrator account.<\/p><\/dd>\n
Yes.\nSome sensitive operations, including rollback and emergency recovery, are restricted to network administrators on multisite installations because those actions can affect plugins shared across the network.<\/p><\/dd>\n
Yes.\nConflict Guard is free to use and does not require a paid subscription to access its core troubleshooting features.<\/p><\/dd>\n
Core diagnostics are performed on your WordPress installation.\nThe plugin communicates with WordPress.org only when you request supported rollback information or download a WordPress.org-hosted plugin version.<\/p><\/dd>\n
Update Conflict Guard to the latest version.\nEarlier versions could encounter this problem when PHP warnings or notices were displayed during REST or AJAX requests. Conflict Guard now prevents those messages from corrupting its JSON responses while continuing to allow PHP errors to be logged normally.\nIf the problem continues, check your PHP error log for the underlying warning.<\/p><\/dd>\n
Conflict Guard removes its plugin data, including its database tables, options, transients, and scheduled events during uninstall.<\/p><\/dd>\n
If Conflict Guard has helped you troubleshoot your website, you can support development through the donation option available in the plugin\u2019s Settings area.<\/p><\/dd>\n\n<\/dl>\n\n\n
Compatibility: Tested and confirmed compatible with WordPress 7.1.\nNo functional changes were required for WordPress 7.1 compatibility.<\/p>\n\n
New: Added a one-time review request after the plugin has been active for 7 days.\nNew: Added a permanent \u201cDon\u2019t ask again\u201d option for the review request.\nNew: Added a Review section in Settings.\nImproved: Existing installations now receive an activation date when upgrading so the review request can work correctly.<\/p>\n\n
Fixed: Stability scores could be reduced permanently by historical errors.\nFixed: Stability scoring now focuses on recent error activity.\nFixed: Repeated instances of the same root-cause error are deduplicated.\nImproved: Stability penalties are capped to prevent a single repeated error from producing an unrealistic score.\nImproved: Diagnostics now displays a clear error message when diagnostic data cannot be loaded.<\/p>\n\n
Fixed: \u201cThe response is not a valid JSON response\u201d errors affecting scans and dashboard actions on some local development environments.\nImproved: REST and AJAX requests no longer allow PHP notices, warnings, or deprecations to corrupt JSON responses.<\/p>\n\n
Fixed: Scanner could incorrectly cache an empty active-plugin list.\nFixed: Scanner and diagnostics could incorrectly read the Safe Mode filtered plugin list.\nFixed: Safe Mode now uses a removable plugin filter.\nImproved: Scan failures now display useful error information instead of failing silently.<\/p>\n\n
Fixed: WooCommerce diagnostics namespace mismatch that could cause a fatal error when WooCommerce was active.<\/p>\n\n
Fixed: Improved SQL safety in uninstall routines.\nFixed: Improved compatibility with WordPress database APIs.\nImproved: Updated documentation around uninstall cleanup.\nFixed: Shortened upgrade notice to comply with WordPress.org limits.<\/p>\n\n
Fixed: Emergency Recovery initialization.\nFixed: Database table creation and dbDelta handling.\nFixed: Multisite activation behavior.\nFixed: Deprecated WordPress rendering API usage.\nImproved: Translation template.\nFixed: Removed an unnecessary empty directory from the plugin package.<\/p>\n\n
Fixed: Improved Emergency Recovery styling and asset loading.\nImproved: Reduced unnecessary WordPress core file loading during rollback operations.\nImproved: Restricted sensitive recovery and plugin-file operations to appropriate administrator capabilities.<\/p>\n\n
Fixed: WordPress.org code-quality compatibility issues.\nImproved: Global variable prefixes.\nImproved: Added External Services documentation.\nImproved: Updated plugin prefixes and WordPress.org compliance.<\/p>\n\n
Initial release.\nAutomatic plugin conflict detection.\nSafe Test Mode.\nSmart conflict isolation.\nPlugin rollback.\nReal-time error monitoring.\nWooCommerce diagnostics.\nEmergency Recovery Mode.\nConflict Timeline.\nPlugin health scoring.\nDiagnostic report export.<\/p>","raw_excerpt":"Find the WordPress plugin breaking your site. Safely detect, isolate, troubleshoot, and roll back plugin conflicts without taking your website offline …","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/316897","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=316897"}],"author":[{"embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/mwangip"}],"wp:attachment":[{"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=316897"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=316897"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=316897"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=316897"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=316897"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/bre.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=316897"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}