WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #42191


Ignore:
Timestamp:
11/03/2017 06:06:47 PM (2 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #42191 – Description

    v1 v2  
    11In follow-up on #42024, an autosave revision is created as part of changeset locking. When a user returns to the customizer after a lock has been lifted, they will be prompted to restore their revision. The restoration logic should only load settings from the changeset which are older than the settings in the `customize_changeset` post (see new setting prop `date_modified_gmt`), or the settings for which there is no existing setting in the changeset. This merge will more intelligently ensure that a user's restored autosave revision won't override the changes another user saved. There may be some cases, however, where selectively restoring parts of an autosave will have unexpected results (e.g. opting to include a newly-created widget, but not accepting the change to the sidebar), so more investigation will be needed.
    22
    3 The problem of conflict resolution in the Customizer is a large problem which is also being worked on in the [Customize Snapshots https://github.com/xwp/wp-customize-snapshots] plugin.
     3The problem of conflict resolution in the Customizer is a large problem which is also being worked on in the [https://github.com/xwp/wp-customize-snapshots Customize Snapshots] plugin.