[wp-trac] [WordPress Trac] #64696: Real time collboration effectively disables persistent post caches while anyone edits a post

WordPress Trac noreply at wordpress.org
Tue Feb 24 21:10:35 UTC 2026


#64696: Real time collboration effectively disables persistent post caches while
anyone edits a post
-------------------------------+--------------------------
 Reporter:  peterwilsoncc      |       Owner:  (none)
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  7.0
Component:  Posts, Post Types  |     Version:  trunk
 Severity:  normal             |  Resolution:
 Keywords:  has-patch          |     Focuses:  performance
-------------------------------+--------------------------

Comment (by peterwilsoncc):

 Replying to [comment:12 westonruter]:
 > ...even with back-off we definitely don't want syncing logic to have any
 impact on the frontend.

 As Dion indicates above, with the heartbeat API there is some amount of
 effect on the front end while editing. The same is true for revisions,
 autosaves and probably a few more things.

 There may be a solution for this by changing how we salt the cache for
 `WP_Query` to reduce invalidation to a subset of queries. A problem for
 another ticket.

 Under no circumstances do I think the solution is to deliberately store
 out of date date in the cache. To do so would replace one bug with
 another.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64696#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list