[wp-trac] [WordPress Trac] #20692: Handle unsaved changes in the customizer

WordPress Trac wp-trac at lists.automattic.com
Wed May 16 20:40:50 UTC 2012


#20692: Handle unsaved changes in the customizer
--------------------------+-----------------
 Reporter:  koopersmith   |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  3.4
Component:  Appearance    |    Version:  3.4
 Severity:  normal        |   Keywords:
--------------------------+-----------------
 Losing your changes is no fun.

 The way I see it, we have two options:

 1) Show an AYS when leaving the customizer by using an onbeforeunload
 handler.
 2) Store unsaved customizations in a customize_data_$stylesheet option.
 The fact that certain customize settings persist across theme changes
 (options) while others don't (theme_mods and some theme-specific options)
 could pose a problem.

 I say let's start with #1.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/20692>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list