| 开发者 | staticguard |
|---|---|
| 更新时间 | 2026年8月31日 22:49 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
uploads/staticguard/. Private releases live in uploads/staticguard/data and the active public copy lives in uploads/staticguard/static/current. Already-deployed wp-content/wordpress-shield-data and wp-content/wordpress-shield-static trees can still be read so a live publication is not moved, but new files are never created there. If uploads are offloaded or stored outside the WordPress web root, StaticGuard reports a blocking admin diagnostic instead of writing to wp-content. On supported servers it adds a clearly delimited routing block to the WordPress .htaccess file. Disabling the plugin removes this managed routing and restores ordinary WordPress delivery.
Security scope
Static publication substantially reduces the code exposed on ordinary public pages, but it does not make the complete WordPress installation invulnerable. Keep WordPress, themes and plugins updated; use strong passwords, backups and HTTPS; and protect the hosting account itself.
Free and Pro
StaticGuard Free contains no paid-feature code and does not contact a license or update server. StaticGuard Pro is a separate GPL extension.
Pro adds:
staticguard folder to /wp-content/plugins/ or install the ZIP from Plugins > Add New > Upload Plugin..htaccess rules. Apache and LiteSpeed are the primary supported targets. A pure Nginx or IIS setup requires server rules that this first release does not install automatically.No. StaticGuard publishes on the current WordPress domain and hosting account.
Yes. Logged-in administrators keep the normal WordPress and Elementor experience. Logged-out visitors receive the static copy.
Yes. The classic Elementor Pro form is supported. StaticGuard keeps its own-site AJAX delivery available and adds an origin check, honeypot and essential rate limiting. Always complete a real delivery test after publication. Atomic forms, third-party form widgets and custom endpoints are outside the guaranteed scope of this first release.
The new build is not activated. If failure happens during public activation, StaticGuard attempts to restore the previous verified copy. The failure remains visible in the deployment history.
StaticGuard does not depend on a specific hosting brand or LiteSpeed. It relies on PHP, writable local storage, readable permalinks and Apache-compatible .htaccess routing. The built-in diagnostic checks the detectable prerequisites, and the first public publication is the final compatibility test.
No. The Free plugin does not send site content, form submissions, telemetry or license requests to StaticGuard. Generated files remain on the WordPress hosting account. Links to documentation and Pro pricing open only when an administrator chooses them.
No. The Free edition reduces exposure of ordinary public pages. WordPress administration and selected dynamic endpoints still exist. Strong passwords, updates and backups remain essential. The optional private back-office address and additional login protections are provided by the separate Pro extension.
uploads/staticguard.wp-content.staticguard-* trees remain readable so a live publication is not moved.staticguard_, including form rate-limit transients.uploads/staticguard, with a fallback for already-deployed staticguard-* folders.