WordPress Blueprints: a real fix for dev environment headaches
Had to onboard a new junior dev last month for a big WooCommerce project. First task was simple: set up the local environment. He’s a…
Tag: APIs
Stop hacking WordPress admin pages: build a class instead
I got a call from a client last week. Their last developer bailed, and they had a “simple” request: add a new delivery option to…
My client’s WooCommerce site crashed. Here’s the real fix.
I got a call from a client in a full-blown panic. Their WooCommerce store, which does huge numbers, was completely down. On Black Friday. They…
Your code is great, so why isn’t it selling?
A buddy of mine, a killer PHP dev, built a WooCommerce extension for subscription invoicing. It was clean, well-documented, and solved a real problem. He…
Let AI do the grunt work: a dev’s take on MCP
I had a client with about a dozen small WordPress sites, nothing major, mostly local businesses. Every month, they wanted a simple health check report….
Using the PHP Reflection API to tame legacy code
I got a call from a client running a membership site on a pretty old, third-party plugin. Their problem? They needed to sync a user’s…
Stop deploying WordPress plugins by hand and use CircleCI instead
I was working on a small security plugin a while back and decided to get it onto the official WordPress directory. But then I remembered…
Build a reusable WordPress meta box class
A client’s Resources section had meta box code scattered across functions.php and two include files, so every small change broke something. One reusable meta box class moved the registration logic into a constructor and the form HTML into a template.
A slow WooCommerce admin is usually a code problem
A client’s high-volume WooCommerce store kept timing out in the admin. More server power didn’t help. The real cause was an N+1 query from a shipping plugin, and the fix was better code, not bigger hosting.
WordPress type safety: when ‘safe’ code fails silently
A junior dev passed a post object where my function wanted an integer, and it failed silently with no error. That is the trap of overly defensive WordPress code, and when you control the environment, failing loudly beats bailing quietly.