[wp-trac] [WordPress Trac] #30529: Customizer: Settings with type 'option' not saved before refresh

[WordPress Trac]

#30529: Customizer: Settings with type 'option' not saved before refresh
-------------------------------+------------------------------
 Reporter:  jaspermdegroot     |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Customize          |     Version:  4.0.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:  administration
-------------------------------+------------------------------

Comment (by jaspermdegroot):

 Thanks for your reply @westonruter and sorry for not including all the
 code. My {{{$wp_customize}}} calls are indeed inside of a
 {{{customize_register}}} action callback function.

 Re: "and also the PHP you're using to read the setting when a refresh
 happens". I don't use anything like that.
 I was about to look into that, but then I noticed that after switching
 from {{{option}}} to {{{theme_mod}}} it wasn't necessary anymore. Changes
 in settings with {{{transport = 'postMessage'}}} were also saved before a
 refresh happened. I was happy with that, but still thought I should report
 the difference that I noticed.

 However, today I created a very basic test case and there the difference
 between type {{{option}}} and {{{theme_mod}}} was gone. In both cases
 changes in settings with {{{postMessage}}} were lost if you didn't save
 before changing things like "Static Front Page" or "Navigation" that use
 {{{refresh}}}.

 I am still debugging to find out what causes the different behaviour in
 the theme I was working on and my basic test case. When I am done I will
 comment again and attach the files.

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