Every WordPress emergency I've seen in the last five years had the same root cause: someone tested an...
Every WordPress emergency I've seen in the last five years had the same root cause: someone tested an update on production.
A staging environment eliminates this. If it breaks on staging, you fix it on staging. Nothing reaches the client's live site until it's verified. Here's how I set one up in 15 minutes.
Why staging isn't optional for client sites
"It worked on my machine" is a joke. "It worked on the live site yesterday" is a client emergency.
The risks of updating production directly:
Clear your calendar, Drupal user: You have a critically urgent patch to install
Drupal to Patch Highly Critical Vulnerability at Risk of Quick Exploitation
Drupal to Release Urgent Core Security Updates on May 20, Sites Told to Prepare
Backup script ingested an accidental asterisk and deleted everything
Drupal critical update to fix bug with high exploitation risk
Most WordPress backup setups fail when they're needed most. The plugin is running. The schedule is...
Most WordPress security advice is useless. "Use a strong password." "Keep plugins updated." "Install...
It was a WordPress site on a $5 DigitalOcean droplet. Client's small business. Nothing fancy. I had...
If you manage WordPress sites for clients, you know the drill. Every month, you log into each site,...
Plugin conflict. Two words that ruin an afternoon. A client calls. Their site is broken -- something...
Before WP-CLI, WordPress maintenance meant: browser open, log in to each site, click Update All,...
