Linux 软件免费装
Banner图

Angry Launch Guard

开发者 thebigbanik
更新时间 2026年10月12日 20:10
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

security launch audit checklist handover

下载

1.0.0

详情介绍:

"Before you hand over the site, check everything." Every agency has launched a site that still said "Discourage search engines", ran in WooCommerce "coming soon" mode, sent order emails from wordpress@, or left a public debug.log behind. Angry Launch Guard runs 41 launch checks in one go and gives you a clear verdict: Each check shows its status, a one-line explanation, and either a Fix button (only where it is safe), clear How to fix instructions, or a link to the right WordPress screen. What it checks Built for handover Safe by design

安装:

  1. Install and activate the plugin.
  2. Go to Tools → Launch Guard.
  3. Optional: add your agency email domains and development domains in the Settings tab.
  4. Press Run audit.

屏幕截图:

  • A check with a one-click fix and its confirmation dialog.
  • Settings: agency email domains, development domains and optional hardening.
  • The Fix log.

常见问题:

Does this replace Site Health?

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.

Does it change my site?

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.

What is the "Angry Hub" menu?

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.

Does it send data anywhere?

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.

Some checks say "Could not check".

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.

The payment gateway check missed my gateway's test mode.

It looks for the common "testmode" and "sandbox" settings. Some gateways use other names, so always double-check each gateway before launch.

Can I add my own checks?

Yes. Use the angry_lg_checks filter to add objects implementing AngryParrot\LaunchGuard\Check (or remove built-in ones).

更新日志:

1.0.0