Importing WordPress data with the strategy pattern
A client needed to import users from a clean CSV and a messy pipe-delimited file. The strategy pattern kept the importer clean instead of a tangle of if/else blocks.
Category: E-commerce Development
Serverless WordPress on AWS for traffic spikes
A client’s WooCommerce site crashed under Black Friday traffic. A serverless AWS stack fixes that scaling problem at the foundation instead of throwing a bigger server at it.
That WooCommerce decimal change that’s silently breaking stores.
Got a call from a long-time client last week. Absolute panic. They’d just run a routine batch of plugin updates, and suddenly their shipping calculator…
That Time a Client’s Coupon Failed During a Flash Sale
Got a call from a client. Total panic. They’d just finished a flash sale for their WooCommerce store, and the star of the show, a…
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…
WordPress serverless hosting: what works and what doesn’t
Had a client call me in a full-blown panic. Their WooCommerce site went down. On Black Friday. They’d just launched a massive sale, got a…
When the WooCommerce admin slows down: a real fix
Had a client come to me with a WooCommerce store that was starting to choke. They had about 30,000 products, and their admin dashboard, specifically…
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.
Custom post types are a persistence layer, not a data dump
Using custom post types as plain data storage scatters your business rules everywhere. Model that logic as PHP entity classes and map the entities onto CPTs instead, so the rules stay in one testable place.