Discuz Plugin Install Doctor
Inspect a local plugin artifact and produce evidence-based findings. Do not modify a live site, database, cache, or uploaded plugin automatically.
Inputs
- - A plugin build directory or ZIP.
- Optional copied error text with passwords, cookies, tokens, IP addresses, and customer data removed.
Run
CODEBLOCK0
Checks
- - JSON metadata shape and
Data.plugin fields. - Plugin directory and module
.inc.php entry consistency. - Conventional install, uninstall, and upgrade files.
- Table declarations,
DB::table() prefix handling, and risky hardcoded prefixes. - Known signatures:
trim(): array given, unknown installfile, missing module file, and missing table.
Recovery
- 1. Fix only findings supported by the package or supplied stack trace.
- Rebuild a new version; do not overwrite the only known-good package.
- Remove the old failed plugin record only through normal Discuz administration and only with administrator approval.
- Clear cache and retry on a matching test site. Preserve production data unless a separately approved migration says otherwise.
Acceptance And Boundaries
- - Exit code 0 means no structural error was detected by these checks; it is not proof of runtime correctness.
- Exit code 2 means one or more blocking findings exist.
- Never execute SQL copied from an error page against production automatically.
- Never bypass application-center validation, permissions, CAPTCHA, or platform review.
