A WooCommerce client needed clean URLs for an old custom event plugin, and the Rewrite API alone kept getting fragile. Here is why a proper object-oriented routing system holds up better as a WordPress site grows into an application.
A WooCommerce add to cart button was failing silently for some users, with no logged errors to go on. Here is how a few lines in wp-config.php turn on WordPress error logging so you can see what is actually breaking on a live site.
A client’s custom events plugin had grown into tangled procedural code that broke every time they touched it. This is how object-oriented programming, and the pattern behind WordPress hooks, keeps a plugin maintainable as it grows.
A client added an email signup form with a heavy marketing plugin and wrecked his site speed. Here’s how to build a lightweight form that posts to your provider’s REST API instead, with full control and no bloat.
Duplicated pricing logic across half a dozen WooCommerce templates turned a 30-minute change into a day of risky edits. The DRY principle, and one function as the single source of truth, is the fix.
A junior dev fixed a 404 by flushing WordPress rewrite rules on every page load, which wrecked performance. Here’s how to register rules on init and flush them only once, when they actually change.
A WooCommerce checkout threw intermittent 500 errors and the logs were useless. Here’s how logging with context, the user, their cart, the gateway, turns a noisy debug.log into error logging you can actually act on.
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 client’s WooCommerce dashboard kept timing out. The cause was a custom framework built for one low-stock widget. Here is how I replaced about a thousand lines with a short function that leans on WordPress and WooCommerce core.
A WooCommerce checkout kept failing silently while a generic PHP error monitor reported zero issues. The cause was a WP_Error the calling code never checked. Here is why WordPress needs monitoring built for it.