Development workflow Intro
Installing WP-CLI, and why local differs from the server
Move click-work to the command line and the work becomes a record. Installing takes ten minutes; deciding which PHP it runs on and as which user saves you…
Technote
Moving click-work to the command line — seeding, migrations, checks and cleanup as reproducible scripts.
8 articles
Development workflow Intro
Move click-work to the command line and the work becomes a record. Installing takes ten minutes; deciding which PHP it runs on and as which user saves you…
Development workflow Intro
Bulk-edit accidents almost always come from selecting the wrong set. Split selection and action into two commands and you get to see what will change before it changes.
Development workflow Practical
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.
Development workflow Practical
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.
Development workflow Practical
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.
Development workflow Advanced
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.
Servers & infrastructure Advanced
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…
Development workflow Advanced
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…