[wp-trac] [WordPress Trac] #31089: Add revisions of settings to the Customizer

[WordPress Trac]

#31089: Add revisions of settings to the Customizer
-------------------------+-----------------------------
 Reporter:  westonruter  |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  javascript
-------------------------+-----------------------------
Changes (by westonruter):

 * milestone:  Awaiting Review => Future Release


Comment:

 @folletto yes! As part of this, I think the “Save & Publish” buttons
 should get split into two separate buttons, like “Save Draft” and
 “Publish” (or “Activate”). The Save Draft button would cause the changeset
 to be stored with a `draft` status instead of `auto-draft` so that it
 wouldn't get garbage-collected. So then I see revisions taking a few
 forms:

 * Previously-published changesets. These are changesets that have gone
 live previously, and thus provide _snapshots_ of changes that went live at
 a given time.
 * Changesets that have the `draft`, `pending`, or `future` status. These
 are essentially revisions that haven't gone live yet.
 * Post revisions of a given changeset. So if you save a draft of a
 changeset, and then continue to make changes and keep hitting Save Draft,
 each time you hit Save can cause a new post revision to be made. Since
 changesets can be edited by multiple people, revisions can indicate who
 made the changes and which settings were modified.

 The Customize Snapshots feature plugin for WP 4.6 re-uses the edit post
 screen in the admin to show the contents of a snapshot (changeset) and
 also shows the core revisions UI for showing changes between the
 revisions. Since the `post_content` is a pretty-printed JSON blob, it
 shows “nicely” in the diff view (if not user-friendly).

 The Customize Snapshots plugin also provides a UI for scheduling a
 snapshot for the future, for submitting a snapshot as Pending (if the user
 lacks `publish_posts` cap), and also for providing a name/title for a
 given snapshot (like a commit message).

 So yeah, I think what is needed is a UI for managing the changesets. For
 listing out existing changesets, the revisions of a changeset, and also a
 UI for transitioning a changeset post from `auto-draft` to `draft`,
 `pending`, or `future`.

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