[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):

 One additional consideration regarding drafting and scheduling in themes
 that are not active yet: changesets cannot currently be scheduled (at an
 architectural level) for themes that are not active, since the settings
 that are defined in the non-active theme are not loaded when WP Cron runs
 to publish the scheduled changeset.

 So currently if you are previewing a theme switch, then the Schedule
 option would initially have to be hidden until we implement #39031 and
 #22880. A summary of that problem I have in a doc:

 > Allow theme switches to be scheduled along with the publishing of other
 settings, also to preview theme switches on the frontend by
 unauthenticated users. — The customizer currently treats the previewed
 “theme” as a separate out-of-band thing that is not included as a setting.
 The previewed theme lives outside the customized state. This means that a
 customize preview for a theme switch can’t be safely shared with a non-
 authenticated user since the user would be able to load any theme they
 want which could be a security concern. Likewise, since the theme isn’t a
 setting in the changeset, scheduling a changeset to go live at a future
 date would not be able to also include the change to the theme. Consider a
 use case of wanting to schedule a Winter theme to a Spring theme, along
 with a change to the Site Logo to have flowers instead of snow.

 It would be very cool eventually to be able to schedule a theme switch
 when this is resolved.

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