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

WordPress Trac noreply at wordpress.org
Fri Sep 8 22:09:06 UTC 2017


#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 melchoyce):

 If we're concerned with letting people undo and redo changes, we should
 consider #21666. Otherwise, if we're just planning on focusing on
 drafting, I think we should simplify down to:

 1. Make changes to your site
 2. Choose "Save Draft" option, rather than "Publish" (I think the split
 button is probably still best for this, if we're staying simple)
 3. When you're ready to push up your changes, switch back to "Publish"

 Or:

 1. Make changes to your site
 2. Decide you don't want to make those changes anymore, and either reload
 the Customizer or leave it
 3. On reload/return to the Customizer, show some sort of "hey, you didn't
 save your changes last time, want to restore?", but otherwise load your
 last published version.

 No trash. No "preview changeset" in the sidebar footer.

 (Essentially, now that I'm re-reviewing the whole thread, this is what I
 originally proposed in [attachment:customizer-drafting-i1.png].)

 ----

 > That is a hard thing to newer users to grasp

 That is hard for ''me'' to grasp, tbh.

 > That may mean that scheduled changes never come in either, since really
 having a scheduled change somewhat precludes there being multiple
 concurrent changesets (branching/non-linear) since you'd probably want to
 new draft changes while you have a previous set of changes already
 scheduled.

 Folks might want to, but we don't have to allow them to. We can choose to
 keep it linear for the sake of simplicity. If we want to include
 previewing and scheduling, I think we're better off refining what
 @JoshuaWold and @folletto were previously exploring. However, I'm totally
 fine with punting those features from 4.9 if we can't get them done in
 time.

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


More information about the wp-trac mailing list