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 rundown of what’s worth caring about in WordPress 6.9: the new Block Processor for faster block parsing, experimental PHP-only blocks, a theme.json fix for Gallery aspect ratios, and why it pays to wait for 6.9.1.
A client needed FAQ rich snippets from the native WordPress Accordion block, without switching to a plugin’s custom block. This shows how to inject Schema.org FAQPage microdata server-side with a render_block filter and WP_HTML_Tag_Processor.
A client wanted an auto-updating copyright block they could edit in the Site Editor. Instead of a full React build, I tried Automattic’s Telex and had an installable plugin in about five minutes. Here’s how it went and where the tool fits.
A client’s inventory sync kept missing its schedule because WP-Cron only runs when someone visits the site. Here’s why that happens and how to move critical jobs to a real server cron job with a standalone PHP script.
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.
An intermittent coupon error at checkout left the logs useless because they had no context. Here’s how structured logging in WordPress captures the user, request, and cart state so you can reproduce and fix the bug.
A real WooCommerce case where two plugins both tried to extend wpdb and only one could win. Here is how the decorator pattern wraps the object instead, so they can stack without breaking each other.
A new client’s WooCommerce checkout was throwing fatal errors after a developer rebuilt field validation from scratch. The fix was not a better library but a short function hooked into WooCommerce, and here is why that was the right call.
A WooCommerce shipping calculator was one 2,000-line file that broke every time a class was added. Refactoring it around a simple interface and small classes fixed that, and it shows how WordPress core can teach better PHP.