A junior dev used the allowed_block_types_all filter globally and it broke the Site Editor. Here is why that happens and how to check the context so you restrict blocks for posts and pages while leaving templates alone.
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 reporting plugin built entirely on the Singleton pattern served stale inventory data across a client’s site. Here’s why singletons hide global state in WordPress, and the static init() method that keeps your classes testable.
A client had a WooCommerce checkout throwing random 500 errors while a 200MB debug log told them nothing. Here is the custom error logging setup I used to catch, count, and get alerted on new errors.
A freelancer rebuilt WooCommerce from scratch and left a store that broke on every plugin update. Here is why building with WordPress hooks and filters beats fighting the framework.
A client WooCommerce checkout kept throwing a random fatal error. The fix was not more code, it was reading the core files first. Why reading code beats writing more of it.
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 had the same widget code copy-pasted twelve times. Here is how I use an abstract base class so one edit updates every widget instead of twelve.
A plugin stuffed 2MB of logs into one autoloaded option and dragged every page down. Here is how the Options API autoload flag works and how to split the data properly.
Hooks buried in class constructors made a WooCommerce plugin impossible to follow. Here is how a small PHP interface and a hook manager give every class a clear, testable contract.