A client’s launch caught on with a subreddit and their $5 shared plan started killing PHP workers, four hours of downtime at the worst moment. No caching code fixes a server with no workers left.
A client’s WordPress.com site outgrew the managed plan after nearly a decade. The XML export timed out and broke thousands of image links, so the move became a SQL migration with a media path filter.
A client’s save button kept spinning with no error at all. The cause was a WP_Error object a plugin ignored, and this is how WordPress fails silently and how to get those errors into your logs.
A WooCommerce Add to Cart button kept turning the wrong color because stylesheets were fighting with !important. Here is how to fix it with CSS specificity and a child theme instead of piling on more overrides.
A developer with a clean WooCommerce plugin sold almost nothing in six months. The problem wasn’t his checkout or his code. Nobody knew who he was, because he kept writing for other developers instead of the people with the problem.
A checkout page went white for some customers and the PHP error log only said what broke, not why. Here’s the case for dedicated error monitoring that captures the full application state at the moment of the crash.
A client wanted one checkout field, and the old code tempted me into a week-long refactor. I shipped the field with two WooCommerce hooks instead, a reminder that a working feature on time beats a perfect rewrite that never ships.
A client WooCommerce order emails looked fine in Apple Mail but broke in Gmail. The reason: Gmail strips CSS from the head. Why inlining your styles is the only reliable fix.
A client’s site kept redirecting to a pharma store no matter how many times they cleaned it. The malware was only the symptom; an outdated plugin left a backdoor open.
I got a call about a membership site that was, for lack of a better term, freaking out. Logged-in users were seeing the public, logged-out…