WordPress plugin API changes break themes

09 November 2026

by deprecating functions and changing defaults. As the CMS evolves, plugin and theme developers must adapt to avoid disrupting sites that depend on their code.

Recent WordPress versions have made major changes that break long-established usage patterns in plugins and themes.

With each release, the WordPress editor, data-modeling interfaces, and JavaScript enqueuing undergo fundamental changes to what works and what doesn't. As a result, sites using plugins that rely on deprecated paths or scripts can break without warning.

WordPress 6.2 brought perhaps the most jarring change — ending support for its core `load-scripts.php` and `load-styles.php` interfaces for concatenating and caching associated and third-party JavaScript and CSS. These PHP scripts responded with a `410 Gone` status for administrators, but for themes relying on output through the `do_concat` filter, or using the print filters for their return value, that meant unexpected breakage. WordPress recommends re-checking your JavaScript and CSS enqueueing, as well as making sure your enqueues aren't relying on these deprecated facilities.

The release of WordPress 6.0 introduced an important change in how developers should think about injecting JavaScript into the editor. Prior to that version, idiosyncrasies in the editor's default rendering meant that it would sometimes inherit the top admin frame. But now, the editor always renders inside an iframe, even with classic meta boxes present, according to developer resources. For developers who overrode some of the structures their themes were supposed to rely on, the editor can appear as a single, unscrollable block, without options to opt into newer features like the permissions API.

If you have JavaScript that operates inside the editor context, developers should make sure it's correctly enqueued via `enqueue_block_editor_assets` and not the older `wp_enqueue_scripts` or `admin_enqueue_scripts`.

Developers relying heavily on in-place editor tweaks may also be adapting to a change in the `@wordpress/dataviews` package. In 6.0, the `groupByField` property was deprecated in favor of an object with `field`, `direction`, and `label` properties. If your plugin or theme performed operations that relied on `groupByField`, you may see empty DataViews, or editor regions where expected data appears blank.

WordPress also modified the REST API with an important change in 2023, when the query parameter `?filter` was removed throughout the API. The WordPress REST API maintains comprehensive changelogs documenting changes to available data, the sets of items served and their structures. Any plugin or theme that relied on `?filter` would likely be affected.

WordPress provides extensive documentation for developers facing breaking changes. The development news and update schedules on the WordPress Developer Blog show detailed documentation is not only recommended, but delivered. The Make WordPress core "Plugin API" section notes that after feature freeze, higher priority is given to fixing regressions (bugs) before other patches.

While these changes are documented and tested for most common use cases, updating plugins may require learning new patterns if you use less common editor features.

As you prepare for updates, here are two resources to start with:

• The full list of all changes in REST API endpoints since 4.7
• Plugin developer improvements in WordPress 6.7

But note that documentation often lags behind changes — if your plugin hasn't been updated since 6.3, it may be worth testing against 6.7 before deployment.