Trim unused WordPress core blocks to speed up the admin
A client’s store had every core block loaded and a sluggish backend to show for it. Here is how we worked out which WordPress core blocks to unregister, and the snippet we used.
Category: Core Updates
Custom block bindings for dynamic content in WordPress 6.9
A client wanted their marketing team to pick which custom product attribute shows on a page, from the editor. Custom block bindings in WordPress 6.9 make that possible, and here is the source registration I used.
Fixing Interactivity API conflicts in WordPress 6.9
How WordPress 6.9’s unique IDs stop Interactivity API directives from clashing on the same element, plus the data-wp-ignore deprecation and new TypeScript helper types.
Smoother Interactivity API navigation in WordPress 6.9
WordPress 6.9 fixes the parts of the Interactivity API that made SPA-like navigation painful: dynamic scripts and stylesheets load on their own, nested router regions update, and a new attachTo property can place a region anywhere.
Why incremental development wins in WordPress
A tiny custom post type tweak turned into a two-month project because we chased perfection instead of shipping. Why incremental development, the way WordPress 6.9 itself is built, works better.
WordPress 6.9 drops IE support: what breaks on old themes
WordPress 6.9 strips out the old Internet Explorer compatibility code. If you run an older custom theme, here is what tends to break and how to audit and modernize the CSS and JavaScript behind it.
Gutenberg block iframe compatibility and your legacy blocks
WordPress is moving the block editor into an iframe in 6.9 and 7.0. Blocks on apiVersion 2 or lower throw warnings now and can break later. Updating to apiVersion 3 is the fix.
Building Gutenberg forms with DataViews in WordPress 6.9
WordPress 6.9 overhauls how you build custom admin forms in Gutenberg. A look at the Field API, DataViews, and DataForm: more field types, rule-based validation, and reusable UI controls that cut the custom code.
Test your site properly before WordPress 6.9
A client deployed WordPress 6.9 RC1 straight to a live WooCommerce store and it broke. The fix is not a rollback, it is a real testing plan: a dedicated environment and conditional code keyed to the WordPress version.
WordPress 6.9 makes accessibility part of the platform
A client’s custom site was failing accessibility checks and getting patched with inline styles and stray aria-hidden. WordPress 6.9 moves much of this into core, from screen reader notifications to live regions, so you build it in by design.