| 开发者 | thebigbanik |
|---|---|
| 更新时间 | 2026年10月12日 20:10 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wordpress@, or left a public debug.log behind. Angry Launch Guard runs 41 launch checks in one go and gives you a clear verdict:
wp-content/debug.log, after confirmation.No. Site Health checks whether WordPress runs well on the server. Launch Guard checks whether a site is ready to hand over to a client: search visibility, sample content, staging leftovers, agency addresses, WooCommerce test modes and so on. Where the two overlap (PHP version, HTTPS) Launch Guard keeps it short and links to Site Health.
Only when you click a Fix button and confirm. Running the audit is read-only. The fixes are listed in the Fix log tab and in the Markdown report.
A small page that lists the Angry Parrot plugins installed on your site, with a link to each one's settings, plus our other plugins. It is built into the plugin (no remote requests) and is shared: with several Angry Parrot plugins installed you still get one menu.
No. The plugin makes requests only to your own site: a few "loopback" requests (for example, to see what a logged-out visitor sees at /wp-json/wp/v2/users) and a TLS handshake with your own domain to read the SSL certificate's expiry date. Update information comes from WordPress' own cached update check. The test email is sent only when you press "Send test email", to the address you enter.
Those checks need the site to load its own pages. Some hosts block these loopback requests. The rest of the audit still runs; Site Health also reports loopback problems.
It looks for the common "testmode" and "sandbox" settings. Some gateways use other names, so always double-check each gateway before launch.
Yes. Use the angry_lg_checks filter to add objects implementing AngryParrot\LaunchGuard\Check (or remove built-in ones).