[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:  Awaiting Review
Component:  Customize              |     Version:  3.4
 Severity:  normal                 |  Resolution:
 Keywords:  has-patch 2nd-opinion  |     Focuses:
-----------------------------------+------------------------------

Comment (by westonruter):

 Replying to [comment:2 engelen]:
 > I agree that there should be a capability for accessing the theme
 customizer, but I don't agree on the naming you propose. In my opinion,
 `customize_theme` would be better-suited for this. With `customize`, it's
 unclear what's being targeted, it could be anything. One could argue that
 naming it `access_theme_customizer`, `use_theme_customizer` or even
 `theme_customizer` would be even better, as it implies even more that it's
 about the theme customizer and not just about "customizing" a theme (which
 could mean anything).

 +1 @celloexpressions

 Also, the term “Theme Customizer” is nowhere to be found in Core for the
 Customizer API. There are a few instances of the term appearing in code
 comments or in translatable strings appearing in the UI, but for the
 underlying Customizer API the namespace is just “customize”, so this seems
 the most logical name for an associated capability.

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