[wp-trac] [WordPress Trac] #56197: Continued post lock data inconsistencies
WordPress Trac
noreply at wordpress.org
Mon Jul 11 18:16:38 UTC 2022
#56197: Continued post lock data inconsistencies
--------------------------+-----------------------------
Reporter: nathan.noom | Owner: SergeyBiryukov
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 6.0.1
Component: Editor | Version: 5.0
Severity: normal | Resolution: fixed
Keywords: has-patch | Focuses:
--------------------------+-----------------------------
Changes (by SergeyBiryukov):
* owner: (none) => SergeyBiryukov
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"53692" 53692]:
{{{
#!CommitTicketReference repository="" revision="53692"
Editor: Include user's name in the `wp_refresh_post_lock()` response.
This ensures that the post lock data returned by the Heartbeat API is
consistent.
Previously, `wp_check_locked_posts()` was updated to return the name of
the user currently editing the post, but the `wp_refresh_post_lock()`
response did not get a similar change.
Follow-up to [53070].
Props nathan.noom.
Fixes #56197.
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/56197#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list