=== GigiHawley Conflict Check for WooCommerce ===
Contributors: gigihawley
Tags: woocommerce, conflict, checkout, safe mode, troubleshooting
Requires at least: 6.4
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Find plugin and theme conflicts on your WooCommerce store without ever touching what your customers see.

== Description ==

WooCommerce stores accumulate plugins fast, and it doesn't take many before something starts breaking — a broken checkout, a duplicate discount, a payment gateway that silently stops working after an update. Finding out *which* plugin is responsible usually means deactivating things one at a time on your live site and hoping nothing goes wrong while you do it.

This plugin does two things instead:

**1. An instant, zero-risk scan.** 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 — it never changes anything on your site.

**2. Safe test mode.** 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*, for up to two hours, and is never written to your site's database. Every other visitor — and every other admin — keeps seeing your store exactly as it is. Close the tab, and it's gone; it also expires automatically even if you don't.

= Why it's built this way =

Nothing is ever written to disk or to your plugin list in the database, and every session expires on its own — there is no way to get stuck with plugins disabled and no way back.

= Built for WooCommerce stores specifically =

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.

== Installation ==

1. Upload the plugin files to `/wp-content/plugins/gigihawley-conflict-check-for-woocommerce`, or install directly through the WordPress plugins screen.
2. Activate the plugin.
3. Go to WooCommerce → Conflict Check.

== Frequently Asked Questions ==

= Will this ever change what my customers see? =

No. The known-conflict scan is read-only. Safe test mode only changes what's visible inside your own logged-in browser session — it is never written to your site's plugin list or database, so no other visitor is ever affected.

= What happens if I close my browser while safe test mode is running? =

The session ends. It also expires automatically after two hours regardless, so there's no way to leave it running by accident.

= Does this replace testing on a staging site? =

For anything you're not sure about, a staging site is still the safest option. Safe test mode is for quick, low-stakes checks — "is it this plugin?" — not a replacement for a full staging environment before a big change.

= Does this check themes too? =

Not yet — the current version checks plugin conflicts. Theme conflict detection is on the roadmap.

== 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.

== Changelog ==

= 0.1.0 =
* Initial release: known-conflict scan and session-scoped safe test mode.

== Upgrade Notice ==

= 0.1.0 =
Initial release.
