WooCommerce 10.4 deprecates wc_enqueue_js(), which always forced a jQuery dependency. Register and enqueue your script, then add inline JS with wp_add_inline_script() so jQuery only loads when needed.
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.
A client got a free five-page site through a WordPress.com Business plan deal. It works for a simple presence, but the moment you need custom PHP, API integrations, or deeper WooCommerce, you hit the limits of a managed build.
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.
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.
A look at what the WordPress 6.9 release candidate phase changes for developers, from the string freeze to which tickets still qualify and the double sign-off needed to backport a fix.
The Interactivity API: This is the big one. For years, if you wanted modern, app-like experiences on your site—like a search filter that updates results…
Why I stopped building one-off REST endpoints for a client AI integration and used the WordPress 6.9 Abilities API instead, with the code to register a single ability.
After watching a junior dev burn hours on Gutenberg boilerplate, I finally tried the AI tools for web development everyone talks about. The two that stuck were Copilot and Cursor.
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.