The small WordPress 6.9 changes that matter for developers
A run through the small WordPress 6.9 changes that actually help developers, from a multisite fix for the News widget to term ID taxonomy templates and a new plugin requirements hook.
A run through the small WordPress 6.9 changes that actually help developers, from a multisite fix for the News widget to term ID taxonomy templates and a new plugin requirements hook.
A client’s membership site was buried under millions of postmeta rows from a badge plugin. Moving that data to a custom table fixed the slowdown, and here’s when it’s worth doing.
WordPress 6.9 ships a Notes feature that keeps editorial feedback inside the block editor instead of scattered across Docs, Asana, and Slack. A look at how it works under the hood and where it still falls short.
An agency told a client WordPress couldn’t handle their e-commerce project. Most WordPress myths about security, speed, and scale come down to bad implementation, not the platform itself.
A WooCommerce migration left European customers’ accented characters showing as garbled symbols. WordPress 6.9 replaces the old guesswork functions with validation, and here’s how to use them.
A WooCommerce store stuffed all its product attributes into post meta, and the filters buckled under thousands of products. The fix was a custom taxonomy for the shared, filterable data.
A client’s save button kept spinning with no error at all. The cause was a WP_Error object a plugin ignored, and this is how WordPress fails silently and how to get those errors into your logs.
A client tried to just translate their WooCommerce shop into German and it broke. Here is why a multilingual WordPress site needs Multisite or a plugin like WPML, and what those tools handle that manual translation cannot.
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.