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

[WordPress Trac]

#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 has-unit-tests  |     Focuses:  performance
--------------------------------------+--------------------------

Comment (by czarate):

 Replying to [comment:132 westonruter]:
 > Something that just came to mind: With the sync data populating post
 meta, will this cause problems for WordPress export/import? Would this
 greatly increase the size of WXR files? Wouldn't all of the sync data be
 completely irrelevant when importing on another site?

 Good call out @westonruter! It will definitely increase the size of WXR
 files. How much depends on how much RTC is used.

 Since WXR imports can result in reassigned database IDs if there are
 conflicts, it's possible that imported sync data would be orphaned or be
 assigned to the wrong post. That won't result in data loss since RTC never
 trusts sync data over the actual post data, but it's an avoidable issue.

 @griffbrad pointed out that we can simply add the sync post meta to the
 existing `wxr_export_skip_postmeta` filter:

 https://github.com/WordPress/wordpress-
 develop/blob/4ac84565c5ce44b917ba88e6556c9434ff7d46a5/src/wp-
 admin/includes/export.php#L492-L498

 If that seems agreeable, I can contribute a patch.

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