18 articles
Knowledge Base
WordPress CLI & API
18 articles in the WordPress CLI & API category.
- WordPress background-process audit — Action Scheduler queue health, WP-Cron, runaway jobs Action Scheduler, WP-Cron, and system cron all run background work on WordPress. The audit that finds the runaway job, the orphaned queue, and the silent cron failure.
- WP-CLI in CI — running site checks, plugin audits, and security scans on every PR WP-CLI is the most under-used quality gate in WordPress. The CI patterns that actually catch the regression before it ships, without doubling the pipeline runtime.
- WP-CLI commands you actually use on cPanel — a practical cheatsheet The WP-CLI commands that come up daily on a managed WordPress on cPanel — core, plugin, theme, user, database, and search-replace — with the flags that matter.
- WordPress REST API — custom endpoints, auth, and rate limits A WordPress REST API custom endpoint is six lines of PHP. Making it survive auth, rate limiting, schema validation, and a public audience is the actual work.
- WordPress WP-CLI batch operations across a fleet of sites Running one WordPress WP-CLI command against one site is easy. Running the same command against 40 sites with rollback, per-host failure handling, and a usable report needs a different shape.
- WordPress WP_DEBUG modes: WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, SCRIPT_DEBUG The four WordPress debug constants do different things, and most installs set them wrong. Here is what each WordPress flag actually toggles, how they interact, and a working pattern.
- WordPress WP-CLI advanced commands — the 15 that earn their keep Past wp plugin list and wp db export, WordPress WP-CLI ships 15 advanced commands that turn a one-off task into a script. The ones that actually move the needle in production.
- WordPress AJAX errors: debugging admin-ajax 400s and 500s WordPress admin-ajax errors hide the real failure behind a 400 or 500. Here is how to debug WordPress AJAX calls — nonce failures, permission checks, and PHP fatals.
- WordPress with Composer — when it's worth the switch Managing WordPress with Composer pays off above a portfolio threshold. The honest decision tree on when to convert a WordPress site to Composer-managed and when to leave it alone.
- WordPress WP-CLI on remote servers via SSH — patterns that hold up WordPress WP-CLI is built to run remotely via SSH using --ssh, alias files, and ~/.wp-cli/config.yml. The patterns that keep one operator command working across 40 servers.
- Installing WP-CLI on a cPanel server the right way How to install WP-CLI on a cPanel server so every account can use it without permission issues, and why a single global install beats per-account copies.
- WordPress deployment automation — GitHub Actions and Bitbucket Pipelines Automating WordPress deployments with GitHub Actions or Bitbucket Pipelines. The pipeline shape that survives plugin updates, database migrations, and a rollback that needs to work on Friday at 5pm.
- Using WP-CLI safely inside a single cPanel account Patterns for running WP-CLI inside a single cPanel account — path discipline, never running as root, and how to keep operations scoped to one site at a time.
- Updating WordPress core via WP-CLI on cPanel The right way to update WordPress core via WP-CLI on a cPanel server — pre-flight checks, the actual commands, and post-update verification.
- Safe WP-CLI batch operations across thousands of objects Running WP-CLI against a few posts is easy. Running it against 300,000 posts or every transient on a site needs throttling, idempotency, and resumability.
- WordPress REST API errors: debugging the rest_no_route, rest_forbidden, and 500s WordPress REST API errors come in a small number of recognizable patterns. Here is how to debug each WordPress REST failure — from rest_no_route to authentication mismatches.
- Bedrock + Composer-managed WordPress for agencies When an agency runs 40 client WordPress sites, the only way to keep them sane is to manage WordPress like any other PHP application — Bedrock layout, Composer for plugin sourcing, env-var-driven config.
- Safely deactivating a WordPress plugin from the command line When wp-admin is down, the right way to disable a misbehaving WordPress plugin is via WP-CLI — not by renaming directories. Here is the procedure that preserves hooks.