[wp-trac] [WordPress Trac] #39896: Customizer: Allow users to Draft changes before Publishing

[WordPress Trac]

#39896: Customizer: Allow users to Draft changes before Publishing
-------------------------+------------------
 Reporter:  melchoyce    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  4.9
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui
-------------------------+------------------

Comment (by westonruter):

 Replying to [comment:23 JoshuaWold]:
 > 1. @westonruter if we go the non-linear route, what do you think about
 having the other changesets at the bottom of this panel? As shown in the
 attachment above.

 Yes, having a list of the other changesets here I think makes sense. Note
 that this list would naturally tie in naturally with adding changeset
 revisions to the Customizer, as a draft/scheduled post are essentially
 revisions that have not yet been published/committed yet. See #21666 and
 #31089.

 > 2. Would we want to give the ability to edit/delete settings?

 Yes, in that it would allow a user to switch to that changeset to make
 additional changes. In other words, it would be like in the Customize
 Snapshots plugin how you can navigate to the list of changesets in the WP
 Admin and click “Customize” to open it in the Customizer to make
 additional changes. The UI for reverting a change from a changeset I think
 would be integrated somewhere else, like within each control for which
 there is a changed/dirty setting there could be a revert button, but that
 can come in a future release. (This capability exists in Customize
 Snapshots today by “inspecting” a changeset in the WP Admin edit post
 screen and clicking the “Remove setting” links.)

 > 3. If I change the changeset to "save draft", what do you think about
 having the option to set the title show?

 See also [https://github.com/xwp/wp-customize-snapshots/issues/152 this
 issue] in Customize Snapshots where the title could potentially default to
 a list of the controls that the user interacted with.

 Being able to specify the title for the changeset would be I think
 important if we go with implementing branching/non-linear changesets. But
 then again, if we do implement branching changesets then what we're going
 to inevitably come up against is conflicts between two separate
 changesets. So part of me thinks that we should go with the linear option
 for 4.9.

 But with the linear option, if there can only ever be one non-published
 changeset at once, would this be inherently problematic for drafted and
 scheduled changesets? If I schedule some changes to go live on Saturday
 night, and today is Thursday, then this would basically block the
 Customizer from being used to make changes until that changeset is
 published since you'd open the Customizer with the scheduled changeset
 loaded in. This wouldn't be a problem for branching changesets, but then
 there would be the issue of how to handle (or not handle) conflicts
 between two unpublished changesets. Some options for conflict resolution
 have been explored/discussed in Customize Snapshots, including adding
 indicators on controls for which there are other changesets which have
 pending changes. Potentially such controls could be “locked” from being
 edited, like post locking, if there is another changeset already has its
 setting as being modified. Anyway, there would be some interesting
 challenges to solve here.

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