starlinewebsolu

Starline Conflict Inspector helps WordPress developers and site administrators identify, diagnose, and resolve plugin-related issues without modifying your site’s files or database.
<h4>Features</h4>
<ul>
<li>
Conflict Scanner — Five automated scans detect duplicate script registrations, multiple jQuery versions/handles, hook crowding (10+ callbacks on high-traffic hooks), deprecated WordPress function usage across active plugins, and version incompatibilities against your WordPress/PHP environment. Results are cached for performance.
</li>
<li>
Diagnostic Mode — Provides guided step-by-step instructions to help you manually isolate plugin conflicts. Uses a session-scoped option (1-hour expiry) — no files are created or plugin states modified. Toggle from the System Health tab or the admin bar.
</li>
<li>
Error Log Analyzer — Parse and browse your WordPress debug.log with severity ratings (critical, error, warning, info), error type badges, plugin attribution, paginated results (20 per page), and expandable stack traces. Handles files up to 10 MB.
</li>
<li>
AI-Powered Diagnostics — Send diagnostic data to OpenAI (GPT-4o, GPT-4o Mini) or Google Gemini (2.0 Flash, 2.5 Pro) for structured analysis. The diagnostic prompt builder redacts absolute paths, API keys, emails, IPs, site URLs, and database credentials before transmission. HTTP requests use <code>wp_remote_post</code> with retry and exponential backoff.
</li>
<li>
System Health Dashboard — View WordPress, PHP, MySQL, and server configuration at a glance along with performance recommendations.
</li>
</ul>
<h4>Privacy & Data Handling</h4>
The plugin performs best-effort redaction of sensitive data before transmission (see “External Services” below). No data is stored or logged server-side by this plugin beyond temporary scan caches (transients, 5-minute TTL) and optional API key storage in the WordPress options table (masked on screen).
<h4>External Services</h4>
This plugin offers optional AI analysis features that transmit diagnostic data to third-party services. No data is sent unless an administrator explicitly configures an API key and clicks Run Full AI Scan.
<h3>OpenAI</h3>
<ul>
<li>Service: OpenAI API (GPT-4o, GPT-4o Mini, GPT-4 Turbo, GPT-3.5 Turbo)</li>
<li>Purpose: Analyze plugin conflict data, PHP error logs, and system diagnostics to identify root causes, severity, and recommended actions.</li>
<li>Data sent: WordPress version, locale, multisite status, debug mode status; PHP version, memory limit, execution time, MySQL version, server software family, OS family; active plugin names and versions; active theme name and version; recent PHP error messages, types, redacted file paths and line numbers. The system instruction and output format specification are also included.</li>
<li>When sent: Only when an administrator clicks “Run Full AI Scan” on the AI Analysis tab.</li>
<li>Data handling: The plugin performs best-effort redaction of absolute file paths, API keys, email addresses, IP addresses, site URLs, database credentials, and WordPress salts before transmission. Redaction uses pattern matching and may not catch all embedded sensitive data, especially in custom error messages or plugin metadata.</li>
<li>Terms of Service: https://openai.com/policies/terms-of-use/</li>
<li>Privacy Policy: https://privacy.openai.com/policies/</li>
</ul>
<h3>Google Gemini</h3>
<ul>
<li>Service: Google Gemini API (Gemini 2.0 Flash, 2.0 Flash-Lite, 2.5 Pro, 1.5 Flash, 1.5 Pro)</li>
<li>Purpose: Same as OpenAI (see above).</li>
<li>Data sent: Same diagnostic data as described for OpenAI.</li>
<li>When sent: Only when an administrator clicks “Run Full AI Scan” on the AI Analysis tab.</li>
<li>Data handling: Same best-effort redaction as described for OpenAI.</li>
<li>Terms of Service: https://cloud.google.com/terms/</li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
You may revoke consent at any time by removing the API key(s) on the AI Analysis settings screen. No diagnostic data is sent to any external service automatically or without explicit administrator action.

Starline Conflict Inspector

Analyze plugin conflicts, PHP errors, JS issues, and performance bottlenecks with AI diagnostics and session-scoped diagnostic mode.

enomoto celtislab

You may have many custom blocking plugins installed, but you may not want (or need) to enable them for all of your posts and pages. This plugin allows you to disable unwanted custom block plugins for each post or page.
Filtering the activation of custom block plugins will allow you to speed up editing in the block editor and use different custom blocks that cause conflicts.
For example, if you use Jetpack plugin, but you don’t need Jetpack custom blocks and you want to clean up your editing screen.
<a href="https://wordpress.org/plugins/plugin-load-filter/" rel="ugc">plugin load filter</a> is recommended for speeding up and controlling the dynamic stopping of plugins on the front side.
For more detailed information, there is an introduction page.
<a href="https://celtislab.net/en/wp-block-editor-assets-filter" rel="nofollow ugc">Documentation</a>

Block editor assets filter

Disable custom blocks not used in block editor editing (Admin Dashboard) to speed up JavaScript and prevent conflicts.

Starline Conflict Inspector vs Block editor assets filter