[wp-trac] [WordPress Trac] #27177: Child themes should inherit parent theme customizer settings on activation / switching

[WordPress Trac]

#27177: Child themes should inherit parent theme customizer settings on activation
/ switching
-------------------------+------------------------------
 Reporter:  krogsgard    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Customize    |     Version:  3.8
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  administration
-------------------------+------------------------------

Comment (by greenshady):

 > ...The customize panel at the very least should include some kind of
 warning that if down the road you decide to use a child theme your
 settings you made in customize are not going to carry over to the child
 theme and you are better off creating the child theme then either editing
 the css directly or using the customize panel at that point.

 This has absolutely nothing to do with the customizer.  The
 title/description of the ticket doesn't accurately describe the "issue".
 The customizer is an options panel (the UI you see when modifying options)
 rather than the data storage/retrieval method.  This about how your theme
 stores settings.  Your theme author could've chosen to store settings via
 the Optiona API, which would carry over into the child theme.

 Theme authors like myself often need default and saved settings that are
 per-theme (e.g., stored on a child theme basis).  That's what the Theme
 Mods API is good for.  It sounds like your theme needed to store options
 using the regular Options API.

 These are not new things.  They've been around for years in WordPress.  If
 you need one method, use it.  If you need another method, use it.

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