| 开发者 | jackofall1232 |
|---|---|
| 更新时间 | 2026年9月15日 05:40 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
information_schema is restricted/wp-content/plugins/, or install it through the Plugins screen.No. Scanning is read-only. Every maintenance action is initiated explicitly by an administrator, handles a bounded batch, and creates a safety snapshot where practical.
No. SAC uses conservative exact-prefix evidence and reports confidence. Unknown data remains unknown, and heuristic ownership never authorizes deletion.
No. Inactive but installed plugins have a distinct status and are not treated as missing.
Table and total-size fields are marked unavailable. Other diagnostics continue to work, and restricted information_schema access is not treated as database failure.
Snapshots are stored locally in a non-autoloaded WordPress option, limited to 20 operations and 14 days, and removed when the plugin is uninstalled. Snapshot values are excluded from exports and AI context.
No. AI is an optional explanation layer. It receives a capped, redacted metadata report only after an administrator requests an explanation. No mutation ability or database credential is exposed.
No. AI UI is enabled only when WordPress reports that configured text generation is supported. All other functionality is independent of AI.
The optional AI features use the WordPress 7.0 AI Client. WordPress needs a text-generation connector configured under Settings → Connectors; the Reports & AI tab links there directly. Every deterministic diagnostic works without it.
Yes. Add add_filter( 'wpdi_read_only', '__return_true' ); in site-specific code.