WP-CLI reference
Every wp ironhelm command, with examples for setting up client sites, importing settings and recovering access from the command line.
All commands start with wp ironhelm. Settings commands use the same checks as the screens.
| Command | What it does |
|---|---|
modules | List features and whether they are on |
enable <id>... and disable <id>... | Turn one or more features on or off |
settings get <id> and settings set <id> <key> <value> | Read or change a feature's settings; secrets are shown masked |
export [<file>] | Save settings to a file; keys and passwords are never included |
import <file> [--dry-run] [--yes] | Load settings, showing every change first |
preset <type> [--level=<level>] [--yes] | Apply settings for business, publisher, shop or community sites, at standard or strict level |
undo | Undo the last bulk change |
cache flush | Clear cached pages and the object cache |
firewall status, block, allow, unblock | See the firewall's state, or manage addresses |
scan files and scan vulnerabilities | Run a security check now |
health | Recalculate and print the health score |
unlock | Clear login lockouts |
2fa-reset <user> | Remove two-step login from an account |
license status, activate <key>, check, deactivate, updates | Manage the API key and look for updates |
Examples
Set up a new client site from your agency's template:
wp ironhelm license activate IHS-XXXX-XXXX-XXXX-XXXX
wp ironhelm import agency-standard.json --yes
wp ironhelm preset business --level=strict --yes
wp ironhelm health
See what an import would change, without applying it:
wp ironhelm import agency-standard.json --dry-run
While a site has no working API key, commands that change settings stop with an explanation; license and the recovery commands always work.