[wp-trac] [WordPress Trac] #64824: User is completely unable to edit content when `wp_enable_real_time_collaboration` is missing from `wp_options`

[WordPress Trac]

#64824: User is completely unable to edit content when
`wp_enable_real_time_collaboration` is missing from `wp_options`
--------------------------+--------------------
 Reporter:  desrosj       |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  7.0
Component:  Editor        |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+--------------------
 When `wp_enable_real_time_collaboration` is not present as an option, the
 editor is unusable because the "Connection lost" screen to be shown almost
 immediately (as soon as the first `wp-json/wp-sync/v1/updates` request
 occurs) and basically prevents the user from editing any post on their
 site.

 I discovered this because my site had `enable_real_time_collaboration` but
 no `wp_enable_real_time_collaboration` present in the options table.

 Here is the timeline of events:
 - Real-time collaboration was first introduced into `trunk` with the
 `enable_real_time_collaboration` option added to the default schema with a
 value of `1` in [61689].
 - The `$db_version` was bumped in [61696].
 - At some point between [61969] and [61702], the nightly build was
 refreshed.
 - The default value was changed to `0` in [61702].
 - Renamed to `wp_enable_real_time_collaboration` in [61722].
 - Removed entirely in [61828].
 - The option was re-added in [61833] as
 `wp_enable_real_time_collaboration` with a default value of `1`, and this
 is the current state (as of [61862]).

 It seems that any site that updated to the nightly build generated between
 19 February and 20 February is likely to not have
 `wp_enable_real_time_collaboration` but `enable_real_time_collaboration`
 instead. The `$db_version` of the site would have updated to `61696`, and
 `wp_enable_real_time_collaboration` never would have made it into the
 database because `populate_options()` only runs when `$db_version` is
 higher than the one stored in the database.

 Related: #64622.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64824>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform