Why the WordPress MVC pattern is usually a mistake
A client site was grinding to a halt because a plugin forced an MVC structure onto WordPress. Why that fights the platform, and why hooks and filters are the WordPress way.
A client site was grinding to a halt because a plugin forced an MVC structure onto WordPress. Why that fights the platform, and why hooks and filters are the WordPress way.
A client’s WooCommerce product filter kept timing out. The fix was not a faster query but a custom taxonomy, and the real story is about designing instead of copy-pasting.
A tangled inventory plugin had hooks and direct class calls everywhere. Treating the WordPress Plugin API as the mediator, with hooks in a dedicated subscriber class, keeps the core logic clean and testable.
A client running Bedrock sites updated by hand and worried about missed patches. I set up Dependabot and CircleCI so Composer updates get opened, tested, and deployed automatically.
I got a Slack message from one of our project managers. A client’s WooCommerce shop, a big one with thousands of products, was crawling. Product…
A WooCommerce coupon worked for regular customers but failed for wholesale ones. Deactivating plugins got me nowhere; stepping through the code with Xdebug found a role-check bug in about 15 minutes.
I was working on a WooCommerce plugin for a client to sync their product inventory with a third-party API. Total classic scenario. The problem was,…
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…
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….
A sharp junior dev was stuck on a bug that only showed up on staging, because he was lost without a GUI. The command line is the most direct way to see what a server is doing, and a couple of basic commands found the error in minutes.