=== Anonindo Conflict Detector ===
Contributors: anonymoustech
Tags: conflict detector, debugging, error log, troubleshooting, plugin conflicts
Requires at least: 6.0
Tested up to: 6.9
Requires PHP: 7.2
Stable tag: 1.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Detect likely plugin conflicts, review logged PHP fatal errors, and follow a safer manual troubleshooting workflow inside WordPress.

== Description ==

Anonindo Conflict Detector helps site owners and developers narrow down plugin conflicts without editing code or guessing blindly.

The plugin records PHP fatal errors, lets administrators scan plugins against recorded error data, and generates practical manual test plans from the WordPress admin area. It also includes a safe mode guide that explains how to isolate issues while staying within WordPress.org plugin guidelines.

This plugin does not automatically deactivate or reactivate other plugins in the WordPress.org version. Instead, it gives you a structured workflow for manual testing so you can identify the likely source of a conflict more safely.

Features:

* Log PHP fatal errors and associate them with the plugin or core path involved.
* Scan installed plugins and mark them as safe or unsafe based on recorded errors.
* View the latest scan report for each plugin from the admin dashboard.
* Generate a binary test plan to split active plugins into smaller troubleshooting groups.
* Generate pair testing suggestions for faster manual conflict isolation.
* Open a safe mode guide that lists active plugins and explains the manual testing sequence.
* Keep troubleshooting data inside your WordPress database.

== Installation ==

1. Upload the plugin files to the `/wp-content/plugins/anonindo-conflict-detector/` directory, or install the plugin through the WordPress plugins screen.
2. Activate the plugin through the `Plugins` screen in WordPress.
3. Open `Conflict Detector` from the WordPress admin menu.
4. Use `Check` to scan individual plugins, or generate a binary or pair testing plan from the dashboard.

== Frequently Asked Questions ==

= What does this plugin detect? =

The plugin helps identify likely plugin conflicts by recording PHP fatal errors and comparing those records against installed plugins.

= Does it automatically disable plugins? =

No. The WordPress.org version does not change the activation state of other plugins. It provides manual testing guidance instead.

= What counts as "unsafe" in a scan? =

A plugin is marked unsafe when recorded PHP errors in the plugin's path have been found in the stored error log.

= Can this detect every type of conflict? =

No. It is most useful for conflicts that produce PHP fatal errors or related crashes. CSS issues, JavaScript-only conflicts, and logic bugs without logged PHP errors may still require manual debugging.

= Who can use the dashboard? =

Only administrators or users with the `manage_options` capability can access the conflict detector tools.

= Where is the troubleshooting data stored? =

The plugin stores error logs and scan results in custom WordPress database tables created on activation.

== Screenshots ==

1. The main Conflict Detector dashboard with scan actions for installed plugins.
2. The generated binary test plan for narrowing down a conflict manually.
3. The pair test suggestions for checking smaller plugin combinations.
4. The safe mode guidance notice with a checklist of plugins to test.

== Changelog ==

= 1.1.0 =

* Renamed plugin constants to avoid activation fatals caused by collisions with other active plugins.
* Refined the manual conflict-testing workflow for the WordPress.org version.
* Expanded readme content and WordPress.org metadata.

= 1.0.1 =

* Adjusted plugin loading and troubleshooting behavior for WordPress.org compliance.

= 1.0.0 =

* Initial release.

== Upgrade Notice ==

= 1.1.0 =

Updates internal constant names to prevent collisions and improves the manual conflict-isolation workflow.
