WordPress 6.9 deprecates the core-data media entity, lets setAttributes take an updater function, and moves SelectControl class names to the root element. Each one can break an existing custom block.
parse_blocks() loads an entire post into memory and can take a server down on large content. WordPress 6.9 adds WP_Block_Processor, a streaming parser that reads block content one pass at a time so you can work with big posts safely.
Gutenberg 22.1 ships a native tabs block and an HTML block that can carry its own CSS and JavaScript. Here is what that means for custom code and how it cuts down on extra plugins.
A client’s custom roles suddenly locked users out after WordPress 6.9 shipped its Abilities API. The fix was to register capabilities and map_meta_cap the way core now expects, not to brute-force add_cap calls.
WordPress 6.9 adds border radius presets to theme.json. Define a set of radius options in your theme, and content editors pick from them instead of typing arbitrary pixel values.
A practical look at the monthly WordPress Core reports: what releases, component activity, and contributor counts actually signal, and how to turn them into decisions for your own projects.
A PHP 8.5 update took down a client’s WooCommerce store. Here is what beta support really means on WordPress 6.9, and how to test the upgrade on staging before it hits your live site.
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.
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.
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.