Technote

WP-CLI automation recipes

Moving click-work to the command line — seeding, migrations, checks and cleanup as reproducible scripts.

8 articles

Development workflow Practical

Safe search-replace: serialisation, guid and dry runs

Replace a domain with raw SQL and widget and theme settings quietly go blank. Serialised data stores string lengths — and switching tools removes the problem entirely.

Developers 9 min read

Development workflow Practical

Running scripts with eval-file, and the argument trap

It runs your own PHP file inside a fully loaded WordPress. Flags starting with -- never reach your script, though, because WP-CLI consumes them first.

Developers 7 min read

Development workflow Practical

Idempotent seeds: running twice must create nothing

A seed script never runs only once. Get the lookup wrong and the check passes, the insert runs, and WordPress quietly appends -2 to the slug.

Developers 9 min read

Development workflow Advanced

Adding your own WP-CLI command to a plugin

Registration is three lines and your docblock becomes the help text. What deserves thought is choosing between log, warning and error — because error stops the run.

Developers 7 min read

Servers & infrastructure Advanced

Moving wp-cron to system cron, and why schedules run late

Scheduled posts that publish late are usually a structural problem, not a code one. WordPress cron rides on incoming requests, so on a quiet site nothing runs at…

Developers 8 min read

Development workflow Advanced

Running WP-CLI in CI: what the checks actually look like

Checks that rely on somebody remembering get skipped in a busy week. Stack the cheap ones first, run the rest against a disposable WordPress, and the remembering stops…

Developers 8 min read

₩270,000 · Join the program