[wp-trac] [WordPress Trac] #39275: Improve wp.customize.previwer.save() for changesets.

[WordPress Trac]

#39275: Improve wp.customize.previwer.save() for changesets.
-------------------------+-----------------------------
 Reporter:  sayedwp      |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Customize    |    Version:  4.7
 Severity:  normal       |   Keywords:
  Focuses:  javascript   |
-------------------------+-----------------------------
 If you do not pass any status in `wp.customize.previwer.save()`  the
 changeset status becomes published because the default `changesetStatus`
 is `publish` in core, which compels you to pass a status if you want to
 save the changeset with any other statuses like `draft/pending/future`
 however that eventually creates a revision. So if you do not want to
 create revisions there is no option except hacking the `customize_save`
 ajax request probably with `$.ajaxPrefilter`.

 So I think if we do not pass any status in `wp.customize.previwer.save()`
 it should just save the changeset to the previous status set.
 Also it would be nice if it had a param like `skip_revision` which skips
 creating new revision.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/39275>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform