[wp-trac] [WordPress Trac] #28605: Introduce customize capability for accessing Customizer

[WordPress Trac]

#28605: Introduce customize capability for accessing Customizer
-----------------------------+------------------
 Reporter:  westonruter      |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  4.0
Component:  Customize        |     Version:  3.4
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------
Changes (by celloexpressions):

 * keywords:  has-patch 2nd-opinion => has-patch
 * milestone:  Awaiting Review => 4.0


Comment:

 Given the current work and future plans for the Customizer, I think we
 should try to get this in sooner rather than later. The fact that
 `customize` could be anything is kind of the point here; the Customizer
 can be used for pretty much anything in WordPress if you try hard enough,
 and within the Customizer access to different panels, sections, and
 settings can be managed at a high level of detail. Decoupling the
 customizer from `edit_theme_options` is an important first step to making
 better use of the Customizer, for both theme-related and theme-independent
 options. I doubt the `capability` parameters in the Customizer API have
 been used much at all because everything is restricted to such a high
 capability currently.

 Moving to 4.0 for now, as this is conceptually pretty critical for the
 long-term goals in improving the Customization experience (see also an
 upcoming make/core post from @westonruter). If lead devs/committers have
 issues with this we can push it back.

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