[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                          |  westonruter
 Priority:  high                                 |      Status:  accepted
Component:  Customize                            |   Milestone:  4.9
 Severity:  normal                               |     Version:
 Keywords:  has-patch needs-testing needs-unit-  |  Resolution:
  tests                                          |     Focuses:  ui
-------------------------------------------------+-------------------------

Comment (by westonruter):

 @bduclos The new features wouldn't really have any impact on the
 implementation of an import/export feature.

 It is trivial to implement an export feature because it's simply a matter
 of exporting the contents of the `customize_changeset` post. Well, and any
 posts that may be referenced in that changeset.

 The hard thing is importing a changeset. Settings for widgets and nav
 menus all make reference to auto-incremented IDs in their settings, and so
 importing a changeset would run the real risk of conflicting with existing
 changes on a given site. Importing a changeset in a way that does not
 conflict with existing content is what the starter content feature was
 designed to solve: #38114.

 In order to export and import a changeset, it would essentially need to be
 able to “understand“ the structure of the IDs (e.g. `nav_menu_item[123]`
 and the structure of the values, like when `page_on_front` is set to `4`,
 that the `123` in the former and the `4` in the latter are both references
 to post IDs. It's the same problem you get when trying to migrate parts of
 a database from one site to another existing database. This is a problem
 that [https://versionpress.net/ VersionPress] has been focused on heavily
 as well as [https://mergebot.com/ Mergebot]. There may be a way to
 leverage schema work done by these projects as a way to inform a changeset
 import/export tool. But it would be out of scope for this ticket.

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