Initial release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The known-conflict scan on the Conflict Check page.","2":"Starting a safe test session.","3":"The safe-mode banner, visible only to the admin running the test."}},"plugin_section":[],"plugin_tags":[3148,191246,54705,8541,286],"plugin_category":[45],"plugin_contributors":[278338],"plugin_business_model":[],"class_list":["post-353138","plugin","type-plugin","status-publish","hentry","plugin_tags-checkout","plugin_tags-conflict","plugin_tags-safe-mode","plugin_tags-troubleshooting","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-gigihawley","plugin_committers-gigihawley"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/gigihawley-conflict-check-for-woocommerce.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
WooCommerce stores accumulate plugins fast, and it doesn't take many before something starts breaking \u2014 a broken checkout, a duplicate discount, a payment gateway that silently stops working after an update. Finding out which<\/em> plugin is responsible usually means deactivating things one at a time on your live site and hoping nothing goes wrong while you do it.<\/p>\n\n This plugin does two things instead:<\/p>\n\n 1. An instant, zero-risk scan.<\/strong> Checks your active plugins against a list of documented, known conflicts (two caching plugins running together, two security firewalls, two SEO plugins fighting over schema markup, and specific vendor-documented pairs like WP Rocket + W3 Total Cache). This is read-only \u2014 it never changes anything on your site.<\/p>\n\n 2. Safe test mode.<\/strong> When the scan isn't enough and you need to actually isolate a plugin, safe test mode lets you do it without risk to your live store: the reduced plugin set is visible only in your own browser session<\/em>, for up to two hours, and is never written to your site's database. Every other visitor \u2014 and every other admin \u2014 keeps seeing your store exactly as it is. Close the tab, and it's gone; it also expires automatically even if you don't.<\/p>\n\n Nothing is ever written to disk or to your plugin list in the database, and every session expires on its own \u2014 there is no way to get stuck with plugins disabled and no way back.<\/p>\n\n General-purpose diagnostic tools treat every WordPress site the same. This one is scoped to WooCommerce stores on purpose: the conflict patterns it checks for, and the language it uses, are about protecting checkout and store functionality, not generic \"something looks wrong\" alerts.<\/p>\n\n\n No. The known-conflict scan is read-only. Safe test mode only changes what's visible inside your own logged-in browser session \u2014 it is never written to your site's plugin list or database, so no other visitor is ever affected.<\/p><\/dd>\n The session ends. It also expires automatically after two hours regardless, so there's no way to leave it running by accident.<\/p><\/dd>\n For anything you're not sure about, a staging site is still the safest option. Safe test mode is for quick, low-stakes checks \u2014 \"is it this plugin?\" \u2014 not a replacement for a full staging environment before a big change.<\/p><\/dd>\n Not yet \u2014 the current version checks plugin conflicts. Theme conflict detection is on the roadmap.<\/p><\/dd>\n\n<\/dl>\n\n\nWhy it's built this way<\/h4>\n\n
Built for WooCommerce stores specifically<\/h4>\n\n
\n
\/wp-content\/plugins\/gigihawley-conflict-check-for-woocommerce<\/code>, or install directly through the WordPress plugins screen.<\/li>\n\n
Will this ever change what my customers see?<\/h3><\/dt>\n
What happens if I close my browser while safe test mode is running?<\/h3><\/dt>\n
Does this replace testing on a staging site?<\/h3><\/dt>\n
Does this check themes too?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n