[wp-trac] [WordPress Trac] #30937: Add Customizer state persistence in changesets (formerly “transactions”)

[WordPress Trac]

#30937: Add Customizer state persistence in changesets (formerly “transactions”)
-------------------------------------------------+-------------------------
 Reporter:  westonruter                          |       Owner:
     Type:  feature request                      |  westonruter
 Priority:  high                                 |      Status:  closed
Component:  Customize                            |   Milestone:  4.7
 Severity:  normal                               |     Version:
 Keywords:  has-patch needs-testing needs-unit-  |  Resolution:  fixed
  tests                                          |     Focuses:
-------------------------------------------------+-------------------------

Comment (by nikeo):

 Replying to [comment:75 westonruter]:
 Hi @westonruter Thanks for this update and explanations. I have a quick
 question about the comment #75 if you don't mind.

 So now the setting changes and the changeset silent updates are 2
 different processes living their own lives.

 When the preview frame gets refreshed with api.previewer.refresh(), the
 dirty settings are always posted (with a temporary {{{<form>}}}), even the
 ones that have been saved in the changeset. Is that correct ?

 I'm currently developing a feature relying server side on the the incoming
 {{{$_POST['customized']}}}
 . I need to know if there's a plan to totally remove this source of
 customized data in the future, or if it will always be available and
 accessible server side. With the current implementation, I plan to do it
 with


 {{{
 $customized_posted_value = $setting -> unsanitized_post_values(
     array(
       'exclude_changeset' => true ,
       'exclude_post_data' => false
     )
   );
 }}}


 Can you also confirm this point ?

 Thanks !

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