Provide "collaborative-editing" post type support #72147
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chriszarate
added
[Feature] Real-time Collaboration
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: +39 B (0%) Total Size: 2.12 MB
ℹ️ View Unchanged
|
Member
|
Recently, we began declaring editor-specific feature supports as sub-properties of top-level Here's the latest example - #71682. |
Contributor
Author
My only reservation is future behavior. In theory, it is possible for a post type to lack |
Member
If that were the case, then the top-level support key would make more sense. The |
chriszarate
force-pushed
the
add/sync-config-enabled-supports
branch
from
5343f57 to
984c700
Compare
chriszarate
force-pushed
the
add/sync-config-enabled-supports
branch
from
984c700 to
75021fd
Compare
This was referenced Oct 10, 2025
Contributor
|
One question I have here is that I have trouble understanding how this support works. Imagine users being in a session (say in the site editor) where some post types support collaborative editing but others not, and they do modifications to both kind of post types, what's the expected behavior here? |
Contributor
Author
Great question! To me, this question centers around edit locks and making sure they are correctly implemented and respected by every editing mode. In general, I would want every editing mode to follow these rules:
Correct me if I'm wrong, but AFAIK the current site editor does not set or respect edit locks. Unintentional overrides are already a problem there. I'm not deeply familiar with the how the site editor works so I'm not sure if I'm suggesting something that will be a huge undertaking. Are there other current examples of multi-entity-editing besides the site editor? In our plugin, we currently disable the experiment on the site editor, partially for this reason. |
Contributor
This is true, even in the post editor it is true. That said when some things are "collaborative" it becomes a bit harder to reason about, because editors have the capacity to open multiple entities from multiple post types at the same time. I guess in other words, it would have been simpler if we had basic collaborative editing for all entities by default (even if the merging is not optimized properly) |
Contributor
Author
|
Closing the PR for this approach, as changing the loaded context to We can work to add |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
Provide a new "collaborative-editing" post type support.
Why?
A new post type support adds support for collaborative editing to posts and pages by default and allows custom post types to opt in to collaborative editing.
How?
Use the
enabledflag on the entity sync config to signal whether an entity supports collaborative editing.Testing Instructions
Testing Instructions for Keyboard
Note: This provider uses requests to admin-ajax.php for signaling and the initial connection is delayed.
Screenshots or screencast
pr-1.mov