설명

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.

스크린샷

The main Conflict Detector dashboard with scan actions for installed plugins.

The generated binary test plan for narrowing down a conflict manually. — The main Conflict Detector dashboard with scan actions for installed plugins.

설치

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

FAQ

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.

후기

이 플러그인에 대한 평가가 없습니다.

기여자 & 개발자

“Anonindo Conflict Detector”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

Akshay Vasoya

자국어로 “Anonindo Conflict Detector”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록을 RSS로 구독하세요.

변경이력

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.

설명

스크린샷

설치

FAQ

What does this plugin detect?

Does it automatically disable plugins?

What counts as “unsafe” in a scan?

Can this detect every type of conflict?

Who can use the dashboard?

Where is the troubleshooting data stored?

후기