| 开发者 | starlinewebsolu |
|---|---|
| 更新时间 | 2026年6月4日 21:28 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
wp_remote_post with retry and exponential backoff.starline-conflict-inspector folder to /wp-content/plugins/.Diagnostic Mode provides step-by-step guided instructions to help you manually isolate plugin conflicts. It does not automatically disable plugins or modify any files. The session expires after 1 hour or when you exit diagnostic mode.
No. The plugin is read-only in its diagnostic functions. The optional Diagnostic Mode feature stores a session-scoped option (1-hour expiry) to track your diagnostic session — no files are created or modified. The only database entries are standard WordPress options for transients (5-minute scan cache), API keys (if configured), and diagnostic mode session tokens.
Yes. API keys are stored in the WordPress options table with autoload disabled, masked on screen (only the last 4 characters shown), and never transmitted to any third party except the configured AI provider when you intentionally run an AI scan.
Go to Tools > Starline Conflict Inspector > AI Analysis, expand your preferred provider section (OpenAI or Gemini), enter your API key, select a model, and click Save AI Settings. The "Run Full AI Scan" button will then be available.
Ensure WP_DEBUG and WP_DEBUG_LOG are set to true in your wp-config.php file. The log file must be located within WP_CONTENT_DIR and be readable by the web server.