Make WordPress Core

Changes between Version 23 and Version 24 of Ticket #31089


Ignore:
Timestamp:
02/16/2017 05:26:29 PM (9 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31089 – Description

    v23 v24  
    1 In #30937 the concept of a “Customizer Transaction” is introduced, wherein each Customizer session gets a changeset containing the settings that are modified and eventually saved (or not). The `customize_changeset` is a custom post type with the settings JSON stored in the `post_content`. Every time the Customizer is accessed, a new `customize_changeset` post is created with `post_status=draft` and then when saving it becomes `post_status=publish`. As such, this automatically becomes a revision history for all saved changes to the Customizer.
     1In #30937 the concept of a “Customize Changeset” is introduced, wherein each Customizer session gets a changeset containing the settings that are modified and eventually saved (or not). The `customize_changeset` is a custom post type with the settings JSON stored in the `post_content`. Every time the Customizer is accessed, a new `customize_changeset` post is created with `post_status=draft` and then when saving it becomes `post_status=publish`. As such, this automatically becomes a revision history for all saved changes to the Customizer.
    22
    33With the work on changesets, however, there is no UI for accessing these revisions. There is no way to see previous revisions, to revert a revision, to recall a revision to continue changes. Nevertheless, UIs for revisions and changeset status changes are being prototyped in the [https://github.com/xwp/wp-customize-snapshots Customize Snapshots] plugin.