Skip to content

Backport: Remove post list lock icon and replace user-specific lock text with RTC enabled#11234

Draft
maxschmeling wants to merge 1 commit intoWordPress:trunkfrom
maxschmeling:backport/rtc-remove-post-lock-icon
Draft

Backport: Remove post list lock icon and replace user-specific lock text with RTC enabled#11234
maxschmeling wants to merge 1 commit intoWordPress:trunkfrom
maxschmeling:backport/rtc-remove-post-lock-icon

Conversation

@maxschmeling
Copy link

Backport WordPress/gutenberg#76322.

When RTC is enabled, the post list should not show an exclusive lock icon or user-specific lock text since multiple users can collaboratively edit the same post.

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

…dicator when RTC is enabled.

When real-time collaboration is enabled, the post list no longer shows exclusive
lock semantics (padlock icon, user avatar, "{user} is currently editing") since
multiple users can collaboratively edit the same post. Instead:

- Shows generic "Currently being edited" text without user-specific info.
- Uses `wp-collaborative-editing` CSS class instead of `wp-locked`, which
  preserves checkbox and row action visibility (no exclusive lock restrictions).
- Changes the "Edit" row action text to "Join" for locked posts.
- Heartbeat responses send generic text with a `collaborative` flag.
- Injects `_wpCollaborationEnabled` into `inline-edit-post` script so the
  heartbeat JS handler applies the correct class on dynamic lock updates.

When RTC is disabled, classic lock behavior is completely unchanged.

Backports WordPress/gutenberg#76322 to core.

Props pkevan.
See #75313.
@github-actions
Copy link

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.

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.

1 participant