Skip to content

Remove real-time collaboration: Backport to the 7.0 branch#11778

Closed
desrosj wants to merge 3 commits intoWordPress:7.0from
desrosj:backport/62334
Closed

Remove real-time collaboration: Backport to the 7.0 branch#11778
desrosj wants to merge 3 commits intoWordPress:7.0from
desrosj:backport/62334

Conversation

@desrosj
Copy link
Copy Markdown
Member

@desrosj desrosj commented May 8, 2026

Stages the backport to the 7.0 branch to resolve merge conflicts

Removes all RTC related code from core. There will still be RTC related code in Gutenberg, but effectively disabled for core since nothing turns it on. The wp.sync global has also been hidden by bundling in WordPress/gutenberg#78085.

Developed in: #11774.

Props maxschmeling, ellatrix, mukesh27.
Fixes #65205.

Trac ticket: Core-65205.

Use of AI Tools


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

Removes all RTC related code from core. There will still be RTC related code in Gutenberg, but effectively disabled for core since nothing turns it on. The wp.sync global has also been hidden by bundling in WordPress/gutenberg#78085.

Developed in: WordPress#11774.

Props maxschmeling, ellatrix, mukesh27.
Fixes #65205.

git-svn-id: https://develop.svn.wordpress.org/trunk@62334 602fd350-edb4-49c9-b593-d223f7449a82
@ellatrix
Copy link
Copy Markdown
Member

ellatrix commented May 8, 2026

Oh, @maxschmeling's branch initially targeted the 7.0 branch, I didn't realize there might be conflicts.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@desrosj
Copy link
Copy Markdown
Member Author

desrosj commented May 8, 2026

Oh, @maxschmeling's branch initially targeted the 7.0 branch, I didn't realize there might be conflicts.

@maxschmeling can you confirm that everything looks good in trunk? If it does, then the process we can follow to backport this one can be:

  • Checkout branches/7.0
  • Run npm run grunt patch:URLOFORIGINALPRWITH7.0ASBASE
  • svn merge -c 62334 --record-only (this will not attempt to actually merge the changes, it only updates the svn:mergeinfo)
  • Commit.

@maxschmeling
Copy link
Copy Markdown

@maxschmeling can you confirm that everything looks good in trunk?

As far as I can tell it is. I tested the PR with the removal. Everything looked good there. And it appears to be applied to trunk correctly.

@maxschmeling
Copy link
Copy Markdown

@maxschmeling can you confirm that everything looks good in trunk?

As far as I can tell it is. I tested the PR with the removal. Everything looked good there. And it appears to be applied to trunk correctly.

I've tested trunk and had Opus take a look too. Not seeing any problems.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 62338
GitHub commit: 2f7a19e

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions Bot closed this May 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants