| 开发者 | wplura |
|---|---|
| 更新时间 | 2026年10月19日 18:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
web-plura-operation-guard folder to /wp-content/plugins/ or install the plugin ZIP in wp-admin.wp web-plura operations status or run fresh local checks with wp web-plura operations scan [section|all]. Developers can register additional local sections with the web_plura_operation_guard_sections filter.No. This local version stores bounded report summaries in WordPress options/transients and does not transmit report payloads externally. Optional telemetry is disabled by default and, if enabled, sends only selected sanitized telemetry categories.
No. It checks local metadata and page markers. It does not read submission bodies, visitor messages, uploaded files, or lead payloads.
It can help review local form, lead capture, SMTP, spam protection, public form page, and outdated form plugin signals. It does not send test submissions or guarantee email delivery.
No. It reviews update readiness signals only. It does not apply updates, modify files, change plugin/theme versions, or run automatic maintenance actions.
Yes. Site Health can show a cached Guard summary after checks have run. It does not run new checks from the Site Health screen.
No. It is a light local guard and checklist. Use dedicated backup, restore, monitoring, and automation tools where those workflows are required.
Yes. It groups local checks for forms, lead capture, digital products, marketplace operations, site systems, Site Health visibility, and update readiness.
Flow Contracts are manual local workflow checks an administrator can create, run, export, and delete from WordPress. For example, a maintainer can record a redacted pre-launch or maintenance-window check, compare it later, and export a CSV handoff without storing form submissions or order payloads. Flow Contracts do not send email, post webhooks, create transactions, schedule checks, or call Cloud in the free plugin.