RTC: REST route for syncing updates returns 404

[mindctrl]

When upgrading from 7.0 Beta 2 to Beta 3, I received a 404 error in the console, related to the sync updates REST route, when adding/editing a page. Others in WP Slack have seen the same issue.

The error was "No route was found matching the URL and request method for this route: /wp-json/wp-sync/v1/updates?_locale=user

Notes

In my case, I checked the state of the Collaboration option (Settings > Writing) before updating. The settings page showed the option enabled. I updated to Beta 3, when to edit a page, and noticed the 404 in the console.

I went back to Settings > Writing, saved the settings, and that fixed the issue. This could have been some old data left around from previous beta testing, but wanted to flag just in case. I tested another site and it did not experience the same issue.

[skithund]

Just to note here that our identical problem was also with 7.0 beta2 to beta3 upgrade, not from 6.9.1.

[amykamala]

Multiple reports of this issue were shared during the 7.0 Beta 3 release party ​here and ​here

[mindctrl]

Another note to confirm upgrading from 6.9.1 to 7.0 Beta 3 worked as expected. This seems like it might be related to the option key changing names in #64622, but we'll need to confirm.

[MadtownLems]

Upgraded from Beta-2 (without enabling RTC) to Beta-3, and immediately started experiencing this issue. Toggling RTC off and back on seems to resolve it.

[aion11]

I upgraded from beta-2 and 6.9.1 and faced this issue on both sites. However, I was testing on localwp, could this be a reason?

[peterwilsoncc]

I've been able to reproduce this by upgrading from WordPress 7.0 Beta 1 to Beta 3, I could not do so from Beta 2. The option name did change in that time to add the wp_ prefix.

For those of you seeing this upgrading from Beta 2, are you running the Gutenberg plugin or just a vanilla WordPress Beta? cc @mindctrl @skithund @MadtownLems

[MadtownLems]

For those of you seeing this upgrading from Beta 2, are you running the Gutenberg plugin or just a vanilla WordPress Beta?

Just a vanilla WP Beta, no Gutenberg plugin

[pbiron]

I've been able to reproduce the problem on a couple of sites that I updated from beta2 to beta3, but not able to reproduce on other sites updated from beta2 to beta3. I can also confirm that on the sites where the problem surfaced, saving Settings > Writing (without changing any of the settings) solved the problem.

All sites are using just the WP beta without GB.

Here's another datapoint: All of the sites where the problem surfaced use Block-based themes, and all of the sites where the problem didn't surface use classic/hybrid themes. Not sure of the significance of that difference, but thought I'd mention it in case it's helpful.

[skithund]

Replying to peterwilsoncc:

For those of you seeing this upgrading from Beta 2, are you running the Gutenberg plugin or just a vanilla WordPress Beta?

Vanilla WP beta with classic/hybrid theme. The site has been through all 7.0 betas at the time of release.

[mindctrl]

When the wp_enable_real_time_collaboration setting is registered in option.php, the default value is set to false, which is the opposite of the intended behavior and the opposite of the default filter fallback in default-filters.php and the default value in populate_options().

Sets the default value of wp_enable_real_time_collaboration to true during setting registration, to match the intended default as set in PR 11161: ​https://github.com/WordPress/wordpress-develop/pull/11161

Core-64814

Trac ticket: https://core.trac.wordpress.org/ticket/64814

## Use of AI Tools
Claude reviewed the phpunit test.

[SergeyBiryukov]

In 61865:

Editor: Correct wp_enable_real_time_collaboration default for REST API sync route.

Follow-up to [61689], [61702], [61722], [61828], [61862], [61864].

Props mindctrl, skithund, amykamala, MadtownLems, aion11, peterwilsoncc, pbiron, apermo, SergeyBiryukov.
Fixes #64814.

[desrosj]

Related #64824.