Title: 2026 – Make WordPress Core

---

#  Yearly Archives: 2026

 [  ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/)
7:22 pm _on_ May 20, 2026     
Tags: 7.1   

# 󠀁[Commence: Operation WP 7.1](https://make.wordpress.org/core/2026/05/20/commence-operation-wp-7-1/)󠁿

With the release of 7.0 earlier today, `trunk` is finally open to any and all commits
for WordPress 7.1.

## Trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is now WordPress 7.1-alpha

While the common practice is for `trunk` to open [once the next release has been branched](https://make.wordpress.org/core/2026/03/27/wordpress-7-0-release-candidate-phase-pt-2/),
closing the primary branchbranch A directory in Subversion. WordPress uses branches
to store the latest development code for each major release (3.9, 4.0, etc.). Branches
are then updated with code for any minor releases of that branch. Sometimes, a major
version of WordPress and its minor versions are collectively referred to as a "branch",
such as "the 4.0 branch". to any commits unrelated to 7.0 was necessary to avoid
making it more complicated to add, modify, or [remove features](https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/)
from the release during the [extension to the cycle](https://make.wordpress.org/core/2026/03/31/extending-the-7-0-cycle/)
to evaluate the state and readiness of the Real-time collaboration feature.

Thank you to everyone for your continued patience.

## Backporting to the numbered branches

As a reminder, the “double signoff” policy applies to changes being made to any 
numbered version branch. The `dev-feedback commit` keywords should be used to request
a second committercommitter A developer with commit access. WordPress has five lead
developers and four permanent core developers with commit access. Additionally, 
the project usually has a few guest or component committers - a developer receiving
commit access, generally for a single release cycle (sometimes renewed) and/or for
a specific component.’s review, with `dev-reviewed` being added after an additional
signoff is given.

More information on this process can be [found in the Make WordPress Core Handbook](https://make.wordpress.org/core/handbook/best-practices/backporting-commits/#backport-process).

_Props [@jorbin](https://profiles.wordpress.org/jorbin/), _[@audrasjb](https://profiles.wordpress.org/audrasjb/)_,_
[@amykamala](https://profiles.wordpress.org/amykamala/), [@4thhubbard](https://profiles.wordpress.org/4thhubbard/),
[@mosescursor](https://profiles.wordpress.org/mosescursor/)_ for peer review._

[#7-1](https://make.wordpress.org/core/tag/7-1/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F20%2Fcommence-operation-wp-7-1%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/amykamala/) [Amy Kamala](https://profiles.wordpress.org/amykamala/)
2:47 am _on_ May 20, 2026     
Tags: [7-0 ( 67 )](https://make.wordpress.org/core/tag/7-0/),
[development ( 17 )](https://make.wordpress.org/core/tag/development/), [dry run ( 6 )](https://make.wordpress.org/core/tag/dry-run/),
[releases ( 57 )](https://make.wordpress.org/core/tag/releases/)   

# 󠀁[WordPress 7.0 Release Day Process](https://make.wordpress.org/core/2026/05/20/wordpress-7-0-release-day-process/)󠁿

[Preparation for the WordPress 7.0](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#pre-final-release)
release is underway.

This post shares the release process, including the timeline and how you can help.

## Release Timeline Overview

 * The [Dry Run](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#dry-run)
   concluded on [ Tuesday, May 19, 2026 at 21:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260519T2100)
 * The 24-hour code freeze is now in effect.
 * The [release party](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#release-day)
   is planned for [ Wednesday, May 20, 2026 at 17:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260520T1700)

---

## 24-Hour Code Freeze

A mandatory 24-hour code freeze will be in effect for the 7.0 branchbranch A directory
in Subversion. WordPress uses branches to store the latest development code for 
each major release (3.9, 4.0, etc.). Branches are then updated with code for any
minor releases of that branch. Sometimes, a major version of WordPress and its minor
versions are collectively referred to as a "branch", such as "the 4.0 branch". after
the Dry Run finishes on April 14th.

What does this mean?

No source code for 7.0 (i.e., in the 7.0 branch) can be changed during these 24 
hours.

#### What happens if a critical bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. is reported during this period?

The release squad will meet with committers and maintainers to determine if the 
issue is a blockerblocker A bug which is so severe that it blocks a release..

 * If yes, another RCrelease candidate One of the final stages in the version release
   cycle, this version signals the potential to be a final release to the public.
   Also see [alpha (beta)](https://make.wordpress.org/core/2026/?output_format=md#alpha-beta).
   release happens, and the release process restarts (meaning the Dry Run repeats,
   and then the 24-hour code freeze clock restarts).
 * If not, then the bug is targeted for 7.1.

## The Release Party

The WordPress 7.0 Release Party will start on [ Wednesday, May 20, 2026 at 17:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260520T1700)
in the [#core Slack channel](https://wordpress.slack.com/archives/C02RQBWTW).

The release party walks through the steps in the [Major Version Release process](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-major-versions/#release-day)
if you want to follow along.

Please note: releasing a major version requires more time than releasing a betaBeta
A pre-release of software that is given out to a large group of users to trial under
real conditions. Beta versions have gone through alpha testing in-house and are 
generally fairly close in look, feel and function to the final product; however,
design changes often occur as part of the process. or release candidaterelease candidate
One of the final stages in the version release cycle, this version signals the potential
to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2026/?output_format=md#alpha-beta)..
There are more steps in the process. If any last-minute issues need addressing, 
those issues will take more time, as well.

## How You Can Help

A key part of the release process is checking that the ZIP packages work on all 
the available server configurations. If you have any of the less commonly used servers
available for testing (IIS, in particular), that would be super helpful. Servers
running older versions of PHPand MySQLMySQL MySQL is a relational database management
system. A database is a structured collection of data where content, configuration
and other options are stored. [https://www.mysql.com](https://www.mysql.com/) will
also need testing.

You can start this early by running the [WordPress 7.0  RC4 packages](https://wordpress.org/download/releases/#betas),
which are built using the same method as the final packages.

During the release party, you will get access to several ways to help test the release
package.

## Tips on What to Test

In particular, testing the following types of installs and updates would be much
appreciated:

 * Does a new WordPress install work correctly? This includes running through the
   manual install process, as well as WP-CLIWP-CLI WP-CLI is the Command Line Interface
   for WordPress, used to do administrative and development tasks in a programmatic
   way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/)
   or one-click installers.
 * Test upgrading from various versions.
 * Remove the wp-config.php file and test a fresh install.
 * Test single site and multisitemultisite Used to describe a WordPress installation
   with a network of multiple blogs, grouped by sites. This installation type has
   shared users tables, and creates separate database tables for each blog (wp_posts
   becomes wp_0_posts). See also **network**, **blog**, **site**/networknetwork (
   versus site, blog)(both subdirectory and subdomain) installations.
 * Does it upgrade correctly?  Are the [files listed in $_old_files](https://core.trac.wordpress.org/browser/branches/7.0/src/wp-admin/includes/update-core.php)
   removed when you upgrade?
 * Does multisite upgrade properly?

Testing the following user flows on both desktop and mobile would be great to validate
each function as expected:

 * Publish a post, including a variety of different blocks.
 * Comment on the post.
 * Install a new pluginPlugin A plugin is a piece of software containing a group
   of functions that can be added to a WordPress website. They can extend functionality
   or add new features to your WordPress websites. WordPress plugins are written
   in the PHP programming language and integrate seamlessly with WordPress. These
   can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party./theme, or upgrade an existing
   one.
 * Change the site language.
 * If you’re a plugin developer, or if there are complex plugins you depend upon,
   test that they’re working correctly.

For a more in-depth list of what features to test, make sure to check the [Help Test WordPress 7.0 post](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/).

_Props to the following for help contributing to this post: @jeffpaul._

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#development](https://make.wordpress.org/core/tag/development/),
[#dry-run](https://make.wordpress.org/core/tag/dry-run/), [#releases](https://make.wordpress.org/core/tag/releases/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F20%2Fwordpress-7-0-release-day-process%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/amykamala/) [Amy Kamala](https://profiles.wordpress.org/amykamala/)
7:42 pm _on_ May 19, 2026     
Tags: [7-0 ( 67 )](https://make.wordpress.org/core/tag/7-0/),
[development ( 17 )](https://make.wordpress.org/core/tag/development/), [release ( 32 )](https://make.wordpress.org/core/tag/release/)

# 󠀁[WordPress 7.0 Release Candidate 5](https://make.wordpress.org/core/2026/05/19/wordpress-7-0-release-candidate-5/)󠁿

WordPress 7.0 RC5 is ready for download and testing!

**This version of the WordPress software is still under development**. Please do
not install, run, or test this version of WordPress on production or mission-critical
websites. Instead, it’s recommended to test RC5 on a test server and site.

WordPress 7.0 RC5 can be tested using any of the following methods:

| **PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.** | Install and activate the[ WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) plugin on a WordPress install. (Select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/2026/?output_format=md#trunk).” channel and “BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2026/?output_format=md#alpha-beta). Only” stream.) | 
| **Direct Download** | Download the [RC5 version (zip)](https://wordpress.org/wordpress-7.0-RC5.zip) and install it on a WordPress website. | 
| **Command Line** | Use this [WP-CLI](https://make.wordpress.org/cli/) command: `wp core update --version=7.0–RC5` | 
| **WordPress Playground** | Use the [WordPress Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) to test the software directly in your browser.  No setup is required – just click and go!  |

The scheduled final release date for WordPress 7.0 **May 20, 2026**. The full [release schedule can be found here](https://make.wordpress.org/core/2026/04/22/wordpress-7-0-release-party-updated-schedule/).
Your help testing Beta and RC versions is vital to making this release as stable
and powerful as possible. Thank you to everyone who helps with testing!

Please continue checking the [Make WordPress Core blog](https://make.wordpress.org/core/)
for [7.0-related posts](https://make.wordpress.org/core/tag/7-0) in the coming weeks
for more information. 

**What’s new in WordPress ****7.0**? Check out the [Field Guide](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/)
for details and highlights.

## This is an extra RC

Testing for issues is critical to the development of any software, and testing works!

This RC is being released to test changes prior to the final release of 7.0.

You can browse the technical details for all issues addressed since Beta 5 using
these links:

 * [Gutenberg commits](https://github.com/WordPress/gutenberg/commits/wp/7.0?since=2026-05-14&until=2026-05-20)
   since May 14, 2026
 * [Closed Trac tickets](https://core.trac.wordpress.org/query?status=closed&changetime=05%2F14%2F2026..05%2F20%2F2026&milestone=7.0&group=component&col=id&col=milestone&col=owner&col=type&col=priority&order=id)
   since May 14, 2026

The 7.0 release is scheduled for Wednesday, May 20th. As always, a successful release
depends on your confirmation during testing. So please download and test!

## How to test this release

Your help testing the WordPress 7.0 RC5 version is key to ensuring that the final
release is the best it can be. While testing the upgrade process is essential, trying
out new features is equally important. This [detailed guide](https://make.wordpress.org/test/2026/02/20/help-test-wordpress-7-0/)
will walk you through testing features in WordPress 7.0.

If you encounter an issue, please report it to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta/)
of the support forums or directly to [WordPress Trac](https://core.trac.wordpress.org/newticket)
if you are comfortable writing a reproducible bugbug A bug is an error or unexpected
result. Performance improvements, code optimization, and are considered enhancements,
not defects. After feature freeze, only bugs are dealt with, with regressions (adverse
changes from the previous version) being the highest priority. report. You can also
check your issue against a list of [known bugs](https://core.trac.wordpress.org/tickets/major).

Curious about testing releases in general? Follow along with the [testing initiatives in Make Core](https://make.wordpress.org/test/)
and join the[ #core-test channel](https://wordpress.slack.com/messages/core-test/)
on[ Making WordPress Slack](https://wordpress.slack.com/).

## A RC5 haiku

_Gift for everyone_

_RC5 shines like the sun_

_Test it and have fun_

_Props to [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/), [@huzaifaalmesbah](https://profiles.wordpress.org/huzaifaalmesbah/)
for proofreading and review._

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#development](https://make.wordpress.org/core/tag/development/),
[#release](https://make.wordpress.org/core/tag/release/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F19%2Fwordpress-7-0-release-candidate-5%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/b1ink0/) [Aditya Dhade](https://profiles.wordpress.org/b1ink0/)
5:31 pm _on_ May 19, 2026     
Tags: [core-performance ( 142 )](https://make.wordpress.org/core/tag/core-performance/),
[hosting ( 47 )](https://make.wordpress.org/core/tag/hosting/), [performance ( 408 )](https://make.wordpress.org/core/tag/performance/),
[performance-chat ( 335 )](https://make.wordpress.org/core/tag/performance-chat/),
[summary ( 969 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[Performance Chat Summary: 19 May 2026](https://make.wordpress.org/core/2026/05/19/performance-chat-summary-19-may-2026/)󠁿

The full chat log is available beginning [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1779206444737629).

## **WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets**

 * [@westonruter](https://profiles.wordpress.org/westonruter/) shared updates related
   to WordPress 7.0 ahead of the scheduled release the next day. Regarding loading
   blockBlock Block is the abstract term used to describe units of markup that, 
   composed together, form the content or layout of a webpage using the WordPress
   editor. The idea combines concepts of what in the past may have achieved with
   shortcodes, custom HTML, and embed discovery into a single consistent API and
   user experience. styles on classic themes, which had several fixes during the
   7.0 release cycle, [@westonruter](https://profiles.wordpress.org/westonruter/)
   updated the [Load Combined Core Block Assets](https://wordpress.org/plugins/load-combined-core-block-assets/)
   pluginPlugin A plugin is a piece of software containing a group of functions 
   that can be added to a WordPress website. They can extend functionality or add
   new features to your WordPress websites. WordPress plugins are written in the
   PHP programming language and integrate seamlessly with WordPress. These can be
   free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. to bump the “Tested up to” version
   and added an inline adminadmin (and super admin) notice for sites on 7.0 with
   the plugin active, asking users to re-check whether the plugin is still needed.

## **Performance Lab Plugin (and other performance plugins)**

 * [@westonruter](https://profiles.wordpress.org/westonruter/) also updated the “
   Tested up to” version for the [Instant Back/Forward](https://wordpress.org/plugins/nocache-bfcache/)
   plugin, which is included among the features listed in Performance Lab. [@westonruter](https://profiles.wordpress.org/westonruter/)
   mentioned that the “Tested up to” versions for the Performance Lab plugins still
   need to be updated on WordPress.orgWordPress.org The community site where WordPress
   code is created and shared by the users. This is where you can download the source
   code for WordPress core, plugins and themes as well as the central location for
   community conversations and organization. [https://wordpress.org/](https://wordpress.org/),
   though the changes had already been done in GitGit Git is a free and open source
   distributed version control system designed to handle everything from small to
   very large projects with speed and efficiency. Git is easy to learn and has a
   tiny footprint with lightning fast performance. Most modern plugin and theme 
   development is being done with this version control system. [https://git-scm.com/](https://git-scm.com/).
 * [@westonruter](https://profiles.wordpress.org/westonruter/) shared that PR [#2469](https://github.com/WordPress/performance/pull/2469)
   bumps the minimum supported PHPPHP The web scripting language in which WordPress
   is primarily architected. WordPress requires PHP 7.4 or higher version in the
   Performance Lab monorepo from PHP 7.2 to PHP 7.4.
 * [@westonruter](https://profiles.wordpress.org/westonruter/) also shared PR [#2479](https://github.com/WordPress/performance/pull/2479),
   which adds an `.npmrc` file to harden npm installs against supply chain attacks.
   Security was improved with `ignore-scripts = true` in the `.npmrc` among other
   enhancements. [@westonruter](https://profiles.wordpress.org/westonruter/) noted
   that this means the pre-commit Husky hooksHooks In WordPress theme and development,
   hooks are functions that can be applied to an action or a Filter in WordPress.
   Actions are functions performed when a certain event occurs in WordPress. Filters
   allow you to modify certain functions. Arguments used to hook both filters and
   actions look the same. are no longer installed automatically, so the handbook
   documentation was updated to mention that `npm run prepare` now needs to be run
   during the initial setup.
 * [@westonruter](https://profiles.wordpress.org/westonruter/) also shared PR [#2482](https://github.com/WordPress/performance/pull/2482),
   which fixes plugin installation and activation flows in Performance Lab when 
   WordPress is using FTPFTP FTP is an acronym for File Transfer Protocol which 
   is a way of moving computer files from one computer to another via the Internet.
   You can use software, known as a FTP client, to upload files to a server for 
   a WordPress website. [https://codex.wordpress.org/FTP_Clients](https://codex.wordpress.org/FTP_Clients)
   filesystem methods such as `ftpext` or `ftpsockets`. The issue was originally
   discovered while testing the new Connectors screen in CoreCore Core is the set
   of software required to run WordPress. The Core Development Team builds WordPress.,
   where provider plugins failed to install. [@westonruter](https://profiles.wordpress.org/westonruter/)
   mentioned that the PR is still being kept as a draft until the related GutenbergGutenberg
   The Gutenberg project is the new Editor Interface for WordPress. The editor improves
   the process and experience of creating new content, making writing rich content
   much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
   HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   PR is merged.
 * [@westonruter](https://profiles.wordpress.org/westonruter/) also shared PR [#2473](https://github.com/WordPress/performance/pull/2473)
   to improve GitHubGitHub GitHub is a website that offers online implementation
   of git repositories that can easily be shared, copied and modified by other developers.
   Public repositories are free to host, private repositories require a paid subscription.
   GitHub introduced the concept of the ‘pull request’ where code changes done in
   branches by contributors can be reviewed and discussed before being merged by
   the repository owner. [https://github.com/](https://github.com/) Copilot usage
   in the Performance Lab repository by pre-warming `wp-env` in the coding agent
   setup steps. [@westonruter](https://profiles.wordpress.org/westonruter/) later
   mentioned that the PR had been approved and was being merged.
 * [@westonruter](https://profiles.wordpress.org/westonruter/) added that several
   PRs still remain in need of review.

## **Open Floor**

 * [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) shared a 
   newly opened issue to explore adding AI based performance recommendations to 
   the plugin when WordPress 7.0 is available and AI is configured [#2485](https://github.com/WordPress/performance/issues/2485)
    - [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) mentioned
      that this may work better as a separate plugin and shared that AI has improved
      enough to provide genuinely useful recommendations to users and potentially
      even fix issues automatically. [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)
      also referenced the earlier [wp-performance-wizard](https://github.com/adamsilverstein/wp-performance-wizard)
      project built two years ago, noting that it already provided good results 
      at the time and that the new idea would likely start with a simpler approach.

**Our next chat will be held on [Tuesday, June 2, 2026 at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260602T1600)
in the [#core-performance channel](https://wordpress.slack.com/messages/core-performance/)
in [Slack](https://make.wordpress.org/chat/)**.

[#core-performance](https://make.wordpress.org/core/tag/core-performance/), [#hosting](https://make.wordpress.org/core/tag/hosting/),
[#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/),
[#summary](https://make.wordpress.org/core/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F19%2Fperformance-chat-summary-19-may-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
6:48 pm _on_ May 18, 2026     
Tags: [make.wordpress.org/ai ( 11 )](https://make.wordpress.org/core/tag/make-wordpress-org-ai/),
[p2-xpost ( 207 )](https://make.wordpress.org/core/tag/p2-xpost/)   

# 󠀁[X-post: Leadership transition for the Core AI team](https://make.wordpress.org/core/2026/05/18/xpost-leadership-transition-for-the-core-ai-team/)󠁿

X-comment from [+make.wordpress.org/ai](https://make.wordpress.org/ai/): Comment
on [Leadership transition for the Core AI team](https://make.wordpress.org/ai/2026/05/18/leadership-transition-for-the-core-ai-team/#comment-136)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F18%2Fxpost-leadership-transition-for-the-core-ai-team%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/sabernhardt/) [Stephen Bernhardt](https://profiles.wordpress.org/sabernhardt/)
3:00 pm _on_ May 14, 2026     
Tags: [7-0 ( 67 )](https://make.wordpress.org/core/tag/7-0/),
[dev-notes ( 618 )](https://make.wordpress.org/core/tag/dev-notes/), [dev-notes-7-0 ( 21 )](https://make.wordpress.org/core/tag/dev-notes-7-0/)

# 󠀁[Removing title attributes in author link functions](https://make.wordpress.org/core/2026/05/14/removing-title-attributes-in-author-link-functions/)󠁿

WordPress 7.0 removes—or facilitates removing—`title` attributes from links relating
to post authors.

## Author’s Website link (from the user profile)

`get_the_author_link()` and `the_author_link()` have a new `$use_title_attr` parameter,
which can be set to `false` to remove the “Visit _Author_’s website” tooltip. By
default, these functions continue to include a `title` attribute.

    ```wp-block-code
    <?php
    // either
    the_author_link();
    // or
    echo get_the_author_link();
    ```

Default output is the same in 7.0 as in 6.9:
`<a href="https://author.example.com"
title="Visit Author&#8217;s website" rel="author external">Author</a>`

    ```wp-block-code
    <?php
    // either
    the_author_link( false );
    // or
    echo get_the_author_link( false );
    ```

Output in 7.0:
`<a href="https://author.example.com" rel="author external">Author
</a>`

## Author’s posts archive link

The “Posts by _Author_” `title` attribute is removed from the link by default. However,
the `title` text is still available for use within the `the_author_posts_link` hook,
along with the author’s display name.

    ```wp-block-code
    <?php
    // either
    the_author_posts_link();
    // or
    echo get_the_author_posts_link();
    ```

Output in 6.9:
`<a href="https://example.org/author/author/" title="Posts by Author"
rel="author">Author</a>`

Output in 7.0:
`<a href="https://example.org/author/author/" rel="author">Author
</a>`

### Editing the posts link text

To replace the author name with the “Posts by _Author_” text, use multiple arguments
in the `the_author_posts_link` filterFilter Filters are one of the two types of 
Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output..

    ```notranslate
    <?php
    /**
     * Edits text for the link to the author page of the author of the current post.
     *
     * Add "Posts by" before the author's display name (or after the name in some translations):
     * `<a href="https://example.org/author/author/" rel="author">Posts by Author</a>`
     *
     * @param string $link   HTML link.
     * @param string $author Author's display name. Default empty string.
     * @param string $title  Text originally used for a title attribute. Default empty string.
     */
    function wpdocs_author_posts_link( $link, $author = '', $title = '' ) {
    	// In WordPress versions prior to 7.0, $author and $title would be empty.
    	if ( '' !== $title && '' !== $author ) {
    		$link = str_replace(
    			'>' . $author . '</a>',
    			'>' . esc_html( $title ) . '</a>', 
    			$link
    		);
    	}

    	return $link;
    }
    add_filter( 'the_author_posts_link', 'wpdocs_author_posts_link', 10, 3 );
    ```

## Authors list HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.

`wp_list_authors()` simply removes the “Posts by _Author_” tooltips.

    ```wp-block-code
    <?php
    wp_list_authors(
    	array(
    		'html' => true // This is true by default.
    	)
    );
    ```

Output in 6.9:
`<li><a href="https://example.org/author/author/" title="Posts by
Author">Author</a></li><li><a href="https://example.org/author/editor/" title="Posts
by Editor">Editor</a></li>`

Output in 7.0:
`<li><a href="https://example.org/author/author/">Author</a></li>
<li><a href="https://example.org/author/editor/">Editor</a></li>`

For more information, refer to [#62835](https://core.trac.wordpress.org/ticket/62835).

---

Props to [@amykamala](https://profiles.wordpress.org/amykamala/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/)
for review.

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/),
[#dev-notes-7-0](https://make.wordpress.org/core/tag/dev-notes-7-0/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F14%2Fremoving-title-attributes-in-author-link-functions%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/amykamala/) [Amy Kamala](https://profiles.wordpress.org/amykamala/)
3:44 am _on_ May 14, 2026     
Tags: [7-0 ( 67 )](https://make.wordpress.org/core/tag/7-0/),
[field guide ( 34 )](https://make.wordpress.org/core/tag/field-guide/)   

# 󠀁[WordPress 7.0 Field Guide](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/)󠁿

This guide outlines major developer features and breaking changes in 7.0 and is 
published in the Release Candidaterelease candidate One of the final stages in the
version release cycle, this version signals the potential to be a final release 
to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2026/?output_format=md#alpha-beta).
phase to help inform WordPress extending developers, CoreCore Core is the set of
software required to run WordPress. The Core Development Team builds WordPress. 
developers, and others.

There are more than [419 Core Trac tickets](https://core.trac.wordpress.org/query?status=closed&milestone=7.0&group=component&col=id&col=summary&col=type&col=priority&col=focuses&order=priority)
included in WordPress 7.0, [over 76 of which are enhancements and feature requests](https://core.trac.wordpress.org/query?status=closed&type=enhancement&type=feature+request&milestone=7.0&group=component&max=200&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority),
and [more than 300 bug fixes](https://core.trac.wordpress.org/query?status=closed&type=defect+(bug)&milestone=7.0&group=component&max=500&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority).
This release includes [40+ tickets focused on the Editor](https://core.trac.wordpress.org/query?status=closed&component=Editor&milestone=7.0&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&order=priority),
and [90+ tickets focused on wp-admin](https://core.trac.wordpress.org/query?component=Administration&milestone=7.0&or&focuses=~administration&milestone=7.0&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority).

Additionally, this release includes [411 enhancements](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Enhancement%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2022.0%22%20OR%20milestone%3A%22Gutenberg%2022.1%22%20OR%20milestone%3A%22Gutenberg%2022.2%22%20OR%20milestone%3A%22Gutenberg%2022.3%22%20OR%20milestone%3A%22Gutenberg%2022.4%22%20OR%20milestone%3A%22Gutenberg%2022.5%22%20OR%20milestone%3A%22Gutenberg%2022.6%22))
and [more than 486 bug fixes](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Bug%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2022.0%22%20OR%20milestone%3A%22Gutenberg%2022.1%22%20OR%20milestone%3A%22Gutenberg%2022.2%22%20OR%20milestone%3A%22Gutenberg%2022.3%22%20OR%20milestone%3A%22Gutenberg%2022.4%22%20OR%20milestone%3A%22Gutenberg%2022.5%22%20OR%20milestone%3A%22Gutenberg%2022.6%22))
for the Editor, Dashboard, and AI integration.

Below is a breakdown of the most important developer-related changes included in
WordPress 7.0.

 1.  [AI building blocks of the future](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#ai-building-blocks-of-the-future)
 2.   a. [WP AI Client](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#wp-ai-client)
      b. [Client-Side Abilities API](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#client-side-abilities-api)
      c. [AI Connectors Screen](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#ai-connectors-screen)
      d. [Connectors API](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#connectors-api)
 3.  [Modernized Dashboard](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#modernized-dashboard)
 4.   a.  [New admin color scheme and styles](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#new-admin-color-scheme-and-styles)
      b.  [View Transitions in WP Admin](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#view-transitions-in-wp-admin)
      c.  [Command Palette shortcut](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#command-palette-shortcut)
      d.  [Font Library](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#font-library)
      e.  [Visual Revisions](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#visual-revisions)
      f.  [Iframed Editor](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#iframed-editor)
      g.  [Custom Navigation Overlays on mobile](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#custom-navigation-overlays-on-mobile)
      h.  [Responsive Editing Mode](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#responsive-editing-mode)
      i.  [Pattern Editing and contentOnly Interactivity](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#pattern-editing-and-contentonly-interactivity)
 5.  [Design Agility](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#design-agility)
 6.   a. [Custom CSS on the block level](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#custom-css-on-the-block-level)
      b. [Headings Block](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#headings-block)
      c. [Breadcrumbs Block](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#breadcrumbs-block)
      d. [Navigation Block](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#navigation-block)
      e. [Video embed cover block ](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#video-embed-cover-block)
      f. [Gallery block ](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#gallery-block)
      g. [Added <p> Block Supports](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#added-p-block-supports)
      h. [Dimensions Support Enhancements](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#dimensions-support-enhancements)
 7.  [Developer’s toolbox](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#developer-s-toolbox)
 8.   a. [PHP Only Block Registration](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#php-only-block-registration)
      b. [Interactivity API](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#interactivity-api)
      c. [DataViews and DataForms ](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#dataviews-and-dataforms)
      d. [Block bindings API iterations ](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#block-bindings-api-iterations)
      e. [New plugin list filter ](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#new-plugin-list-filter)
      f. [Site Editor wordpress/build and routing](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#site-editor-wordpress-build-and-routing)
 9.  [Bonus dev goodies](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#bonus-dev-goodies)
 10.  a. [Block Hooks for content-like Custom Post Types.](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#block-hooks-for-content-like-custom-post-types)
      b. [More secure user registration](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#more-secure-user-registration)
      c. [CodeMirror Update to v5](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#codemirror-update-to-v5)
      d. [External Libraries Updates](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#external-libraries-updates)
      e. [PHP Updates](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#php-updates)
 11. [Accessibility](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#accessibility)
 12. [But wait, there’s more!](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/#but-wait-there-s-more)

## AI building blocks of the future

Step into a new era with WordPress 7.0, shipped with AI integration and abilities.
Provider-agnostic architecture gives you full control over units and capabilitiescapability
A **capability** is permission to perform one or more types of task. Checking if
a user has a capability is performed by the `current_user_can` function. Each user
of a WordPress site might have some permissions but not others, depending on their
role. For example, users who have the Author role usually have permission to edit
their own posts (the “edit_posts” capability), but not permission to edit other 
users’ posts (the “edit_others_posts” capability). while tapping into the endless
opportunities AI can bring to life. These critical building blocks are just the 
beginning, paving the way for agentic collaborators and so much more.

### WP AI Client

WordPress 7.0 unlocks AI capabilities right in your website. The new WP AI client
adds a central interface that lets plugins communicate with generative AI models
while remaining provider-agnostic. WordPress Core handles request routing for you.
Managed in the `Settings > Connectors` screen with APIAPI An API or Application 
Programming Interface is a software intermediary that allows programs to interact
with each other and share data in limited, clearly defined ways. keys funneled through
the Connectors API, you can start with some preset models and add your favorites.

As a bonus, the Abilities API is integrated directly into the WP AI Client, delivering
new and expansive AI abilities that can be built into workflows that run abilities
fluidly, one after another.

[[

PluginPlugin A plugin is a piece of software containing a group of functions that
can be added to a WordPress website. They can extend functionality or add new features
to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. developers can use the new `using_model_preference()`
function to indicate which models to use in order of preference, then add feature
detection to match capabilities against available models – lowering cost and speeding
up processing time. The AI Client includes a series of advanced configuration controls,
and a `WP_AI_Client_Prompt_Builder` class for calling methods. For easy upgrades,
the `wordpress/wp-ai-client` package handles transitioning to 7.0 automatically.

> [Introducing the AI Client in WordPress 7.0](https://make.wordpress.org/core/2026/03/24/introducing-the-ai-client-in-wordpress-7-0/)

### Client-Side Abilities API

WordPress 7.0 expands on the Abilities API by introducing a JavaScriptJavaScript
JavaScript or JS is an object-oriented computer programming language commonly used
to create interactive effects within web browsers. WordPress makes extensive use
of JS for a better user experience. While PHP is executed on the server, JS executes
within a user’s browser. [https://www.javascript.com](https://www.javascript.com/)
counterpart: the Client-Side Abilities package with new and hybrid abilities, an
intuitive UIUI User interface, a command palette, and filterFilter Filters are one
of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output. and query functionality.

Plugin developers can enqueue `@wordpress/core-abilities` to automatically fetch
and register server-side abilities via the REST APIREST API The REST API is an acronym
for the RESTful Application Program Interface (API) that uses HTTP requests to GET,
PUT, POST and DELETE data. It is how the front end of an application (think “phone
app” or “website”) can communicate with the data store (think “database” or “file
system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/),
or enqueue only `@wordpress/abilities` to work with the plugin’s client-side abilities.
Registered abilities are organized in customizable categories, and abilities and
categories can be unregistered via the PHPPHP The web scripting language in which
WordPress is primarily architected. WordPress requires PHP 7.4 or higher API.  MetaMeta
Meta is a term that refers to the inside workings of a group. For us, this is the
team that works on internal WordPress sites like WordCamp Central and Make WordPress.
data annotation is supported, and `core/abilities` makes `useSelect` available for
reactive queries in ReactReact React is a JavaScript library that makes it easy 
to reason about, construct, and maintain stateless and stateful user interfaces.
[https://reactjs.org](https://reactjs.org/) components.

> [Client-Side Abilities API in WordPress 7.0](https://make.wordpress.org/core/2026/03/24/client-side-abilities-api-in-wordpress-7-0/)

### AI Connectors Screen

Manage all of your AI provider connections in one place on the new Connectors screen.
Found under `Settings > Connectors` in the dashboard, the screen gives you everything
you need to manage your connections. Registered connectors are displayed automatically
on the page, and so is detailed registry meta data in a card format. The Connectors
screen includes three default providers: Anthropic, Google, and OpenAI, while also
allowing users to configure their own connections.

[⌊WP 7.0 Connectors Screen⌉⌊WP 7.0 Connectors Screen⌉[

### Connectors API

The Connectors API is the backbone of the Connectors screen; an extensibility API
that facilitates and supports the inclusion of agents.

The API supports two authentication methods (`api_key` and `none`) based on provider
metadata, and is designed to facilitate additional connector types in future releases.
The Connectors API uses the WP AI Client’s default registry to automatically discover
providers, and corresponding metadata to generate connectors, while connectors authenticated
via other methods are stored in the PHP registry. You can use the `wp_connectors_init`
action to override connectors metadata, which will be the key for registering new
connector types in future releases. The API includes three public functions for 
querying the registry, and the frontend UI can be customized using client-side JavaScript
registration.

> [Introducing the Connectors API in WordPress 7.0](https://make.wordpress.org/core/2026/03/18/introducing-the-connectors-api-in-wordpress-7-0/)

## Modernized Dashboard

WordPress 7.0 delivers an upgraded adminadmin (and super admin) experience, with
a sleek, new color scheme named “Modern”, numerous enhancements throughout the dashboard,
and seamless visual transitions as you navigate from screen to screen. A new Command
Palette shortcut in the upper admin bar lets you access tools from anywhere in the
dashboard, while a new dedicated dashboard page for font management centralizes 
and simplifies managing fonts. The enhanced iframed post editor stabilizes the screen,
while editors leave comments on blocks, receive notifications for notes and even
visually compare two revision versions.

### New admin color scheme and styles

WordPress administration has been reinvigorated with a new, chic color scheme throughout
the dashboard. The new Modern admin theme is live across admin headers, the CustomizerCustomizer
Tool built into WordPress core that hooks into most modern themes. You can use it
to preview and modify many of your site’s appearance settings., the color scheme
picker, script loader, various user functions, and even the multisitemultisite Used
to describe a WordPress installation with a network of multiple blogs, grouped by
sites. This installation type has shared users tables, and creates separate database
tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**,**
site** user signup has been reskinned. The Modern theme is clean and easy on the
eyes, boasting a refreshed color palette, higher contrast, and upgraded typography,
uplifting and elevating the admin experience.

[[

### View Transitions in WP Admin

Navigating the dashboard is a smooth ride in 7.0. User views slide from one screen
to the next as you move across wp-admin. Cross-document view transitions use distinct
transition names for admin menu items in order to facilitate this simple visual 
slide effect, firing when the active submenu changes between screens. With consideration
for all users, View Transitions are only activated if a preference is not set for
reduced motion on the OS level.

### Command Palette shortcut

Access your editing toolset from anywhere in the dashboard with a single click of
the new Command Palette shortcut. WordPress 7.0 includes a `⌘K` or `Ctrl+K` icon
for logged-in users in the upper admin bar, which unfurls the command palette on
click. The new shortcut speedruns editing and gives full control from anywhere in
the dash: while building, designing or simply browsing notes.

[[

### Font Library

The Font Library has expanded in 7.0 with the introduction of a dedicated font management
page. Now you and your team can manage, upload and install fonts from one place 
in blockBlock Block is the abstract term used to describe units of markup that, 
composed together, form the content or layout of a webpage using the WordPress editor.
The idea combines concepts of what in the past may have achieved with shortcodes,
custom HTML, and embed discovery into a single consistent API and user experience.,
hybrid and classic themes.

[[

### Visual RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

In WordPress 7.0, Visual Revisions make editing easier and more intuitive, while
adding insight into post or page edit history. Users can now visually compare two
revision versions directly in the Editor using a slider bar to visually switch between
revisions. The document inspector shows a summary of changes, while color indicators
and sizes of changes can be seen for each location, jumping to that location on 
the page when clicked.

[[

### Iframed Editor

An improved, iframed editor in 7.0 offers more stability to the post editor experience.
An iframed post editor is now enforced when all Block API blocks inserted into the
post are using `version 3` of the API or higher. If not, the iframeiframe iFrame
is an acronym for an inline frame. An iFrame is used inside a webpage to load another
HTML document and render it. This HTML document may also contain JavaScript and/
or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.
is removed, upholding backwards compatibility for lower-versioned blocks.

> [Iframed Editor Changes in WordPress 7.0](https://make.wordpress.org/core/2026/02/24/iframed-editor-changes-in-wordpress-7-0/)

# Creative Customization

7.0 inspires creativity with enhanced design tools and new editing capabilities.
Users can now customize navigation overlays on mobile, granular control of the responsiveness
for individual blocks, and edit at the pattern level in different modes.

### Custom Navigation Overlays on mobile

Hamburger menu overlays can now be customized and built from blocks and patterns
in the Site Editor, with a dedicated Navigation Overlay Close block for placing 
and styling a close button anywhere within the overlay, giving users and theme authors
flexibility to define mobile navigation experiences. In-place overlay selection 
and previews create a seamless editing experience, while users can review and assign
overlays, and themes can offer default templates for quick setup.

> [Customizable Navigation Overlays in WordPress 7.0](https://make.wordpress.org/core/2026/03/04/customisable-navigation-overlays-in-wordpress-7-0/)

### Responsive Editing Mode

WordPress 7.0 introduces customizable block visibility based on device type, allowing
editors to hide or reveal blocks by device, without affecting other viewports. Controls
to launch a block visibility options modal are available in the block toolbar, block
inspector sidebarSidebar A sidebar in WordPress is referred to a widget-ready area
used by WordPress themes to display information that is not a part of the main content.
It is not always a vertical column on the side. It can be a horizontal rectangle
below or above the content area, footer, header, or any where in the theme., and
command palette. Icons are displayed in List View next to blocks that have active
visibility rules, indicating what viewports they are being hidden on.

Offering even more responsiveness enhancements, 7.0 introduces the ability to change
styles for different breakpoints, customize breakpoint sizes and more.

> [Block Visibility in WordPress 7.0](https://make.wordpress.org/core/2026/03/15/block-visibility-in-wordpress-7-0/)

### Pattern Editing and `contentOnly` Interactivity

7.0 introduces Pattern Overrides for custom blocks, Pattern-level editing modes 
for contextual and symbol patterns, a parent-child tree view for buttons and list
blocks, and the ability to opt out of `contentOnly` mode.

`contentOnly` mode will now be default for patterns that previously relied on unrestricted
editing of their inner blocks, while a new `disableContentOnlyForUnsyncedPatterns`
setting or `block_editor_settings_all` PHP filter allows `contentOnly` mode to be
opted out of for unsynced patterns.

In 7.0 `contentOnly` mode is applied more broadly, so if a block is nested in a `
contentOnly` pattern, plugin developers will want to ensure attributes representing
the block’s content have `"role": "content" ` set in `block.json` to retain their
ability to be edited and prevent them from being hidden in list view.

Block developers can now add a `"listView": true` block supports declaration to 
add a `List View` tab to the block inspector with a dedicated view for the block
that allows editors to update and customize the block more easily.

> [Pattern Editing in WordPress 7.0](https://make.wordpress.org/core/2026/03/15/pattern-editing-in-wordpress-7-0/)

Block attributes that support Block Bindings now also support Pattern Overrides 
for custom blocks. Pattern Overrides now apply to any block, including custom blocks,
and can be opted-in through `block_bindings_supported_attributes` filter(s). Attribute
values appear in the rendered blocks’ markup for dynamic and static blocks, and 
if static blocks have more complex attributes than the HTMLHTML HyperText Markup
Language. The semantic scripting language primarily used for outputting content 
in web browsers. API can process, a `render_callback()` function can be used to 
ensure bound attribute values render.

> [Pattern Overrides in WP 7.0: Support for Custom Blocks](https://make.wordpress.org/core/2026/03/16/pattern-overrides-in-wp-7-0-support-for-custom-blocks/)

## Design Agility

Designing in WordPress 7.0 has become more flexible with the introduction of new
blocks, new block supports and new design tools. A new Heading block, Icons block,
and Breadcrumbs block are shipped with 7.0, with added lightbox support for the 
Gallery block, and dynamic URLURL A specific web address of a website or web page
on the Internet, such as a website’s URL www.wordpress.org support in the Navigation
Link block. 7.0 includes text line indent support, text column support, dimensions
width and height support, dimension presets, tools and controls, and aspect ratios
for wide and full images.

### Custom CSSCSS Cascading Style Sheets. on the block level

7.0 introduces the ability for custom CSS to be applied on-page to individual blocks.
This allows granular control over every detail of your content, with quick and intuitive
access to style controls.

[[

### Headings Block

A new Heading Block includes variations of all heading levels, easy toggling in 
the sidebar inspector and quick transforms, and display in the search and slash 
inserter.

[[

### Breadcrumbs Block

The new Breadcrumbs Block in 7.0 automatically reflects the site’s navigational 
hierarchy with the ability for global application in site parts like the theme headerHeader
The header of your site is typically the first thing people will experience. The
masthead or header art located across the top of your page is part of the look and
feel of your website. It can influence a visitor’s opinion about your content and
you/ your organization’s brand. It may also look different on different screen sizes..
New filters allow developers to add, remove, and modify breadcrumb trails, and specify
which taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress,
some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies).
and terms appear in the Breadcrumbs trails.

> [Breadcrumb block filters](https://make.wordpress.org/core/2026/03/04/breadcrumb-block-filters/)

### Navigation Block

Editing the navigation block is now more simple with improved insertion, Interactivity
for pattern editing and ContentOnly, and improved “bound” page items presentation.

### Video embed cover block 

Videos can now be embedded as section backgrounds in the Cover block. 

### Gallery block 

The Gallery block now has lightbox support with an added slideshow option. Just 
create and insert a Gallery, click the link icon and then hit ‘enlarge on click’.

[⌊.0 Gallery lightbox slideshow image⌉⌊.0 Gallery lightbox slideshow image⌉[

### Added `<p>` Block Supports

Text in the Paragraph block can now be arranged in a columns layout, and opt-in `
textIndent` block support for typography has been introduced.

> [New Block Support: Text Indent (textIndent)](https://make.wordpress.org/core/2026/03/15/new-block-support-text-indent-textindent/)

More details on new and improved blocks are available here:

> [Roster of design tools per block (WordPress 7.0 edition)](https://make.wordpress.org/core/2026/04/22/roster-of-design-tools-per-block-wordpress-7-0/)

### Dimensions Support Enhancements

7.0 introduces height and width block support, typography text indent support in
paragraphs, presets support, and pseudo elements support on the core/button block
for ( `':hover`‘, `':focus`‘, `':focus-visible'`, `':active' `) at the `theme.json`
level. Support for preset dimensions values in `theme.json` have been added for 
block supports such as width, height and min-height, allowing the block’s variations
to control the same pseudo elements, while a defined set of preset values for dimensions
block supports can be leveraged to reduce the need to know and manually set the 
same value across multiple blocks.

> [Dimensions Support Enhancements in WordPress 7.0](https://make.wordpress.org/core/2026/03/15/dimensions-support-enhancements-in-wordpress-7-0/)

## Developer’s toolbox

7.0 delivers an expansive developer toolbox including new tools for building, enhanced
supportive structures, and expanded API abilities. Developers can now create a PHP-
only representation of blocks on the server level, customize plugin list filters,
and explore the foundational layout for a more extensibleExtensible This is the 
ability to add additional functionality to the code. Plugins extend the WordPress
core software. Site Editor.

### PHP Only Block Registration

WordPress 7.0 allows blocks and patterns to be created directly on the server with
PHP, and registered with the Block API. The PHP-only representation of blocks and
patterns includes pattern creation and syntax that streamlines block creation and
bindings, registering blocks automatically When a block declares `'supports' => 
array( 'autoRegister' => true )` along with a render callback, exposing it to the
client-side via a JavaScript global variable. PHP-registered block attributes can
be edited in the editor and inspector controls can be generated from attributes,
with automatic DataForm inspector controls added for PHP auto-registered blocks.

> [PHP-only block registration](https://make.wordpress.org/core/2026/03/03/php-only-block-registration/)

### Interactivity API

Introducing a new `watch()` function to the `@wordpress/interactivity` package that
subscribes to changes in any signal accessed inside a callback, re-running the callback
whenever those signals change. The API’s `data-wp-watch` can be added to a DOM element’s
lifecycle and react to state changes. The `state.url` value is now populated server-
side during directive processing, remaining unchanged until the first client-side
navigation occurs.

> [Changes to the Interactivity API in WordPress 7.0](https://make.wordpress.org/core/2026/02/23/changes-to-the-interactivity-api-in-wordpress-7-0/)

### DataViews and DataForms 

Experience a new Activity layout, new Details layout, Improved modal appearance,
and the ability to register 3rd party types in the Field API.

> [DataViews, DataForm, et al. in WordPress 7.0](https://make.wordpress.org/core/2026/03/04/dataviews-dataform-et-al-in-wordpress-7-0/)

### Block bindings API iterations 

Introducing the Block bindings and patterns overrides feature, with the ability 
to filter available attribute sources by format, aligning with the Field API.

### New plugin list filter 

A new `plugins_list_status_text` filter in `get_views()` has been added to allow
custom filtering. Custom statuses added with `plugins_list` now appear as tabs to
filter the related plugins. The tab label can be customized using the new `plugins_list_status_text`
hook.

### Site Editor wordpress/build and routing

In 7.0 the foundation has been laid for an extensible site editor and routing, route
validation, a new `@wordpress/boot package` that allows plugins to build custom 
site-editor pages, and a refactored `@wordpress/scripts` that builds from directories
and reduces Webpack dependence.

## Bonus dev goodies

WordPress 7.0 introduces updates that span every area of Core. These changes support
ongoing initiatives to create a flexible foundation for developers while boosting
usability and opportunity.

### Block HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. for content-like Custom Post Types.

The Block Hooks logic has been moved from individual post type filters to the REST
controller.

### More secure user registration

Administrator and Editor roles have been removed from the new user default selector
under `General` in the admin screen. Site Health now alerts if one of those roles
was selected before updating, while a new `default_role_dropdown_excluded_roles`
filter allows developers to change default excluded roles.

### CodeMirror Update to v5

CodeMirror has been updated to the latest `v5` version, along with `CSSLint`, `HTMLHint`,
and J`SONLint`, while `Esprima` has been replaced with `Espree` for ES6 support 
and JavaScript linting.

### External Libraries Updates

 * [backbone.js has been upgraded](https://core.trac.wordpress.org/ticket/63763)
   to the latest version (1.6.1).
 * The Requests library has been updated from 2.0.11 to [2.0.17](https://github.com/WordPress/Requests/releases/tag/v2.0.17).

### PHP Updates

 * WordPress Core’s [minimum PHP version is now 7.4](https://make.wordpress.org/core/2026/01/09/dropping-support-for-php-7-2-and-7-3/)
 * [PHPMailer has been updated](https://core.trac.wordpress.org/ticket/64491) to
   version 7.0.2, which includes a Sender address bugbug A bug is an error or unexpected
   result. Performance improvements, code optimization, and are considered enhancements,
   not defects. After feature freeze, only bugs are dealt with, with regressions(
   adverse changes from the previous version) being the highest priority. fix.

## AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)

WordPress 7.0 includes numerous improvements and additions that make content more
accessible for everyone. The login password reset now pre-populates with a username
to comply with WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines.
These guidelines are helping make sure the internet is accessible to all people 
no matter how they would need to access the internet (screen-reader, keyboard only,
etc) [https://www.w3.org/TR/WCAG21/](https://www.w3.org/TR/WCAG21/). 2.2, and a 
new `wp_get_image_alttext()` function imports Image Alt text metadata from image
IPTC metadata. The `word-break` property has been added to `.screen-reader-text`
to ensure screen readers won’t read text as individual letters in hidden text, and
[view transitions are only activated when reduced motion is not set](https://core.trac.wordpress.org/ticket/64529).

Title attributes can now be removed from two functions using a new `$use_title_attr`
parameter, and are removed from three author link functions by default.

## But wait, there’s more!

7.0 offers so much more! More than [300](https://core.trac.wordpress.org/query?status=closed&type=defect+(bug)&milestone=7.0&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority)
Core bugs, [486](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Bug%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2022.0%22%20OR%20milestone%3A%22Gutenberg%2022.1%22%20OR%20milestone%3A%22Gutenberg%2022.2%22%20OR%20milestone%3A%22Gutenberg%2022.3%22%20OR%20milestone%3A%22Gutenberg%2022.4%22%20OR%20milestone%3A%22Gutenberg%2022.5%22%20OR%20milestone%3A%22Gutenberg%2022.6%22))
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
The editor improves the process and experience of creating new content, making writing
rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes,
custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
bugs, [77](https://core.trac.wordpress.org/query?status=closed&type=enhancement&type=feature+request&milestone=7.0&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority)
enhancements and feature requests, and [35](https://core.trac.wordpress.org/query?status=closed&type=task+(blessed)&milestone=7.0&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority)
blessed tasks have been [marked as fixed in WordPress 7.0](https://core.trac.wordpress.org/query?status=closed&milestone=7.0&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority).

Below are a few to highlight:

 * Site Health: OPCache added to `Site Health > Info > Server` ([Trac #63697](https://core.trac.wordpress.org/ticket/63697))
 * Editor: Name/description metadata added to patterns when saved ([Trac #64123](https://core.trac.wordpress.org/ticket/64123))
 * Script Loader: Allow scripts to depend on modules: ([Trac #61500](https://core.trac.wordpress.org/ticket/61500))
 * Script Loader: HTML5 script theme support deprecated and removed ([Trac #64442](https://core.trac.wordpress.org/ticket/64442))
 * General: Allow hooking into `wp_trigger_error()` when `WP_DEBUG` is not truthy.(
   [Trac #60886](https://core.trac.wordpress.org/ticket/60886)) 
 * Multisite: Networks and Sites no longer automatically mark website as spam when
   an account is marked as spam ([Trac #61146](https://core.trac.wordpress.org/ticket/61146))
 * Themes: PHP 8.1 deprecation notice handling ([Trac #64864](https://core.trac.wordpress.org/ticket/64864))
 * Editor: Bottom margins removed from all components, and margin-free styles are
   now default. ([GB #39358](https://github.com/WordPress/gutenberg/issues/39358#issue-1165672375))

**_Thank you to everyone who contributed to this version of WordPress, whether through
code, testing, or something else – your contributions matter and help Make WordPress._**

_Props to [@westonruter](https://profiles.wordpress.org/westonruter/), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/),
[@marybaum](https://profiles.wordpress.org/marybaum/), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/),
[@jorbin](https://profiles.wordpress.org/jorbin/), [@desrosj](https://profiles.wordpress.org/desrosj/),__
[@coffee2code](https://profiles.wordpress.org/coffee2code/), [@audrasjb](https://profiles.wordpress.org/audrasjb/),
[@wildworks](https://profiles.wordpress.org/wildworks/) and [@ankit-k-gupta](https://profiles.wordpress.org/ankit-k-gupta/)
for collaboration and review._

_Edit 5/17/26: Add DataViews dev notedev note Each important change in WordPress
Core is documented in a developers note, (usually called dev note). Good dev notes
generally include a description of the change, the decision that led to this change,
and a description of how developers are supposed to work with that change. Dev notes
are published on Make/Core blog during the beta phase of WordPress release cycle.
Publishing dev notes is particularly important when plugin/theme authors and WordPress
developers need to be aware of those changes.In general, all dev notes are compiled
into a Field Guide at the beginning of the release candidate phase., update Connectors
screen image, add textIndent block support dev note, remove mention of playlist 
block, add mention of margin-free styles default._

_Edit 5/18/26 Remove Notes section, insert new Gallery block slideshow image_

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#field-guide](https://make.wordpress.org/core/tag/field-guide/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F14%2Fwordpress-7-0-field-guide%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
3:55 am _on_ May 13, 2026     
Tags: [7-0 ( 67 )](https://make.wordpress.org/core/tag/7-0/),
[agenda ( 1,128 )](https://make.wordpress.org/core/tag/agenda/), [core ( 727 )](https://make.wordpress.org/core/tag/core/),
[dev chat ( 905 )](https://make.wordpress.org/core/tag/dev-chat/)   

# 󠀁[Dev Chat Agenda – May 13, 2026](https://make.wordpress.org/core/2026/05/13/dev-chat-agenda-may-13-2026/)󠁿

The next WordPress Developers Chat will take place on [Wednesday, May 13, 2026, at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260513T1500)
in the [core](https://wordpress.slack.com/messages/core/) channel on [Make WordPress Slack](https://make.wordpress.org/chat/).

The live meeting will focus on the discussion for upcoming releases, and have an
open floor section.

The various curated agenda sections below refer to additional items. If you have
ticketticket Created for both bug reports and feature development on the bug tracker.
requests for help, please continue to post details in the comments section at the
end of this agenda or bring them up during the dev chat.

## Announcements 📢

### WordPress 7.0 Updates

 * [Real-time collaboration will not ship in WordPress 7.0](https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/)
 * [7.0 RC3 released May 8th](https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/)
 * [Results: Real Time Collaboration performance testing analysis](https://make.wordpress.org/core/2026/05/08/results-real-time-collaboration-performance-testing-analysis/)
 * [WordPress 7.0 Release Party Updated Schedule](https://make.wordpress.org/core/2026/04/22/wordpress-7-0-release-party-updated-schedule/)

### General announcements

 * [What’s new in Gutenberg 23.1? (07 May)](https://make.wordpress.org/core/2026/05/07/whats-new-in-gutenberg-23-1-07-may/)

## Discussions 💬

_The discussion section of the agenda is for discussing important topics affecting
the upcoming release or larger initiatives that impact the CoreCore Core is the 
set of software required to run WordPress. The Core Development Team builds WordPress.
Team. To nominate a topic for discussion, please leave a comment on this agenda 
with a summary of the topic, any relevant links that will help people get context
for the discussion, and what kind of feedback you are looking for from others participating
in the discussion_.

## Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for 
assistance on tickets. Tickets in the milestone for the next major or maintenance
release will be prioritized.
Please include details of tickets / PRs and the links
in the comments, and indicate whether you intend to be available during the meeting
for discussion or will be async.

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#agenda](https://make.wordpress.org/core/tag/agenda/),
[#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F13%2Fdev-chat-agenda-may-13-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
3:46 am _on_ May 13, 2026     
Tags: [7-0 ( 67 )](https://make.wordpress.org/core/tag/7-0/),
[core ( 727 )](https://make.wordpress.org/core/tag/core/), [core-editor ( 748 )](https://make.wordpress.org/core/tag/core-editor/),
[dev chat ( 905 )](https://make.wordpress.org/core/tag/dev-chat/)   

# 󠀁[Dev Chat summary: May 6, 2026](https://make.wordpress.org/core/2026/05/13/summary-dev-chat-may-6-2026/)󠁿

[Start](https://wordpress.slack.com/archives/C02RQBWTW/p1778079614514649) of the
meeting in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/),
facilitated by [@audrasjb](https://profiles.wordpress.org/audrasjb/) 🔗 [Agenda post](https://make.wordpress.org/core/2026/05/06/dev-chat-agenda-may-6/).

## Announcements 📢

### WordPress 7.0 Updates

 * [RC3 (“new Beta 1”) scheduled for this Friday, May 8th](https://make.wordpress.org/core/2026/04/22/wordpress-7-0-release-party-updated-schedule/)
 * [Call for RTC testing from hosts](https://make.wordpress.org/hosting/2026/04/29/urgent-testing-request-to-web-hosts-for-collaborative-editing-by-may-4th/).
   Submissions still welcome. Thank you to Bluehost, Kinsta, XServer, GoDaddy,WordPress.
   comWordPress.com An online implementation of WordPress code that lets you immediately
   access a new WordPress environment to publish your content. WordPress.com is 
   a private company owned by Automattic that hosts the largest multisite in the
   world. This is arguably the best place to start blogging if you have never touched
   WordPress before. [https://wordpress.com/](https://wordpress.com/), Ionos, and
   any other hosts for helping test RTC.
 * A decision about RTC introduction is about to be finalized (and [it was finalized](https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/)).
   See ticketticket Created for both bug reports and feature development on the 
   bug tracker. [#64696](https://core.trac.wordpress.org/ticket/64696).

### General

 * A new [proposal to auto-generate Block Editor Handbook docs from block.json](https://make.wordpress.org/core/2026/05/05/proposal-auto-generate-block-editor-handbook-docs-from-block-json/)
   was published.
 * For folks who have helped with a Contributor DayContributor Day Contributor Days
   are standalone days, frequently held before or after WordCamps but they can also
   happen at any time. They are events where people get together to work on various
   areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are
   many teams that people can participate in, each with a different focus. [https://2017.us.wordcamp.org/contributor-day/](https://2017.us.wordcamp.org/contributor-day/)
   [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)
   table, please take a look at [Help us help others contribute to WordPress](https://make.wordpress.org/project/2026/04/23/help-us-help-others-contribute-to-wordpress/)
   and consider helping out with this initiative, which is part of a larger effort
   to make it easier for people to start contributing.

## Discussion 💬

[@desrosj](https://profiles.wordpress.org/desrosj/) noticed there are [still 37 open tickets in milestone 7.0](https://core.trac.wordpress.org/tickets/major/workflow)
and that the statuts of the about page ticket ([#64536](https://core.trac.wordpress.org/ticket/64536))
wasn’t clear.

[@jorbin](https://profiles.wordpress.org/jorbin/) proposed to run a dedicated 7.0
scrub after the chat.

[@juanmaguitar](https://profiles.wordpress.org/juanmaguitar/) will host a dedicated
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
The editor improves the process and experience of creating new content, making writing
rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes,
custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
scrub on Thursday.

[@jorbin](https://profiles.wordpress.org/jorbin/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/)
asked about the Field GuideField guide The field guide is a type of blogpost published
on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/).
The field guide generally lists all the dev notes published during the beta cycle.
This guide is linked in the about page of the corresponding version of WordPress,
in the release post and in the HelpHub version page. timeline. It is currently under
review and should be published ASAP.

---

[@joefusco](https://profiles.wordpress.org/joefusco/) asked: “Is there a process
for getting systems team feedback on the RTC custom table?  The code and testing
infrastructure are ready, including a standalone testing pluginPlugin A plugin is
a piece of software containing a group of functions that can be added to a WordPress
website. They can extend functionality or add new features to your WordPress websites.
WordPress plugins are written in the PHP programming language and integrate seamlessly
with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. that can run on production sites
without changes to trunktrunk A directory in Subversion containing the latest development
code in preparation for the next major release cycle. If you are running "trunk",
then you are on the latest revision..  I’m not sure who to direct this to or what
the next gate is in the process.”

[@desrosj](https://profiles.wordpress.org/desrosj/) answered the systems team has
been involved with the discussions and I know that they have been testing.

[@joefusco](https://profiles.wordpress.org/joefusco/) replied “Mainly whether there
are any outstanding concerns with the table structure or the approach that would
prevent it from landing in 7.0.  Also, is there a documented process for new table
proposals that require systems review?  This won’t be the last time a feature needs
a schema change, and it would help future contributors know the path.”

Several attendees noted that it’s likely not worth the effort to formalize a process,
as that kind of change doesn’t occur regularly.

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#core](https://make.wordpress.org/core/tag/core/),
[#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F13%2Fsummary-dev-chat-may-6-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
1:02 am _on_ May 8, 2026     
Tags: [feature-real-time-collaboration ( 3 )](https://make.wordpress.org/core/tag/feature-real-time-collaboration/)

# 󠀁[Results: Real Time Collaboration performance testing analysis](https://make.wordpress.org/core/2026/05/08/results-real-time-collaboration-performance-testing-analysis/)󠁿

Following the decision to [remove real-time collaboration from WordPress 7.0,](https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/)
this post summarizes what the latest hosting test data showed and outlines the recommended
storage strategy for future iteration. A huge thank you to every web host that submitted
results in response to last week’s call for testing. Submissions came in from eight
hosting environments between April 29 and May 4, and analysis of the aggregated,
anonymized data is now complete. Based on the results, the recommendation is to 
use `custom-table-with-transients` as the default RTC storage strategy for continued
testing and future iteration.

As a reminder, four candidate storage strategies for the [Real Time Collaboration (“RTC”)](https://make.wordpress.org/core/2026/03/10/real-time-collaboration-in-the-block-editor/)
feature were tested under load:

 * `post-meta` — the RC2 baseline.
 * `custom-table` — a dedicated table for all RTC data.
 * `post-meta-transients` — post metaMeta Meta is a term that refers to the inside
   workings of a group. For us, this is the team that works on internal WordPress
   sites like WordCamp Central and Make WordPress. for storage with transients for
   client awareness.
 * `custom-table-with-transients` — a dedicated table with an object cache-backed
   awareness (Note: while contributors have been referring to this as a transient
   approach, it is a convenient short hand rather than a technical description)

The test runner captured per-request REST dispatch time and database query counts
during sustained 30-second polling windows. Eight complete captures from a mix of
shared, shared-with-Redis, managed-cloud, and no-object-cache environments form 
the basis of the analysis below.

## **What the data showed**

Across the cohort, **`custom-table-with-transients` was first or tied-first on six
of seven complete environments**, and was never slower than the RC2 baseline (`post-
meta` approach). On average, the `custom-table-with-transients` approach was ~52%
faster and the purely `custom-table` approach was ~37% faster than the current implementation.
On hosts without a persistent object cache, it landed within 0.05–0.17 ms of plain`
custom-table`—close enough that the two are effectively tied where caching is absent.

Two clean signals showed up in the database query counts during dispatch:

 1. With a persistent object cache present, both transient-based strategies dropped
    to a single database query per dispatch.
 2. Independent of caching, the `custom-table` schema cut the query count roughly in
    half compared to the post-meta strategies.

`custom-table-with-transients` wins because it gets the schema reduction when caching
is absent, and the cache reduction when it’s present. `post-meta-transients`, by
contrast, is not recommended even as a fallback. It nearly doubles in latency without
a persistent cache, and on one no-cache shared environment it exhibited a pathological
transient code path that pushed dispatch latency past 26 ms — several times worse
than any other strategy on that host.

## **Recommendation for the future**

The recommended storage strategy `custom-table-with-transients` is considered the
best case among the candidates. It wins decisively on environments with a persistent
object cache, remains comfortably ahead of the baseline on environments without 
one, and degrades gracefully across the full spread of hosting tiers represented
in the data.

## **Read the full analysis**

The full anonymized analysis—including per-environment dispatch tables, query counts,
cross-cuts comparing cache effects, and bootstrap floors—is available [here](https://gist.github.com/dd32/bd15729b7de1e842cc8de9b2f875a63f).
All submissions remain anonymized in line with the commitment made in the original
call for testing.

## **Summary**

The data from this testing window was sufficient to make the call confidently: `
custom-table-with-transients` is the best option forward as the default for real
time collaboration. When work resumes after clean up from 7.0, this is the approach
best positioned to explore more deeply next.

Thank you again to every host that participated. Your contributions provided the
data needed to make this storage recommendation and will help set real-time collaboration
up for success across the wide range of environments where WordPress runs. Props
to Ionos, BlueHost, Kinsta, XServer, and WordPress.comWordPress.com An online implementation
of WordPress code that lets you immediately access a new WordPress environment to
publish your content. WordPress.com is a private company owned by Automattic that
hosts the largest multisite in the world. This is arguably the best place to start
blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/)
for their contributions here.

_Props to [@griffbrad](https://profiles.wordpress.org/griffbrad/) for drafting this
post. Props to [@dd32](https://profiles.wordpress.org/dd32/) [@desrosj](https://profiles.wordpress.org/desrosj/)
[@jmdodd](https://profiles.wordpress.org/jmdodd/) [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)
[@jorbin](https://profiles.wordpress.org/jorbin/) [@4thhubbard](https://profiles.wordpress.org/4thhubbard/)
for testing, analysis, and review. If I missed your name, please tell me as it’s
a mistake and there have been a lot of moving pieces._

[#feature-real-time-collaboration](https://make.wordpress.org/core/tag/feature-real-time-collaboration/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F08%2Fresults-real-time-collaboration-performance-testing-analysis%2F%23respond&locale=en_US)

# Post navigation

[← Older posts](https://make.wordpress.org/core/2026/page/2/?output_format=md)