[wp-trac] [WordPress Trac] #39335: Twenty Seventeen: customize-controls.js incorrectly assumes theme_options section is always present

[WordPress Trac]

#39335: Twenty Seventeen: customize-controls.js incorrectly assumes theme_options
section is always present
---------------------------+----------------------------
 Reporter:  westonruter    |       Owner:  davidakennedy
     Type:  defect (bug)   |      Status:  reviewing
 Priority:  normal         |   Milestone:  4.7.1
Component:  Bundled Theme  |     Version:  4.7
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:
---------------------------+----------------------------
Changes (by westonruter):

 * keywords:   => has-patch
 * owner:   => davidakennedy
 * status:  new => reviewing


Old description:

> Plugins can de-register panels, sections, controls, and settings that are
> registered by default by core and by themes. As such, themes should use
> the deferred pattern to interact with such constructs. This is
> particularly an issue in Twenty Seventeen and now it assumes the
> `theme_options` section is present.

New description:

 Plugins can de-register panels, sections, controls, and settings that are
 registered by default by core and by themes. As such, themes should use
 the deferred pattern to interact with such constructs. This is
 particularly an issue in Twenty Seventeen and now it assumes the
 `theme_options` section is present.

 Originally reported at https://github.com/xwp/wp-customizer-blank-
 slate/issues/8

--

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