A client wanted their block plugin hosted under the WordPress GitHub organization and found the path opaque. Here are the actual criteria: community ownership, a sponsoring Make team, more than one maintainer, and what happens when maintenance stops.
A client’s store slowed to a crawl right after someone clicked update to WooCommerce 10.4. Here is what the release actually changes in the REST API, the Store API and the block editor, and which custom code you should review first.
A WooCommerce shop inherited custom plugins that broke on every update and dragged the admin down. The fix was not more hotfixes, it was the basics: prefixed functions, core hooks, sanitized input and capability checks.
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.
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 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.
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.
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.