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

WordPress Trac noreply at wordpress.org
Wed Jul 9 19:04:54 UTC 2014


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

 * keywords:  has-patch => has-patch 2nd-opinion
 * type:  feature request => enhancement


Comment:

 In lieu of making this a new primitive capability, what if it were a meta
 capability mapped to 'edit_theme_options'?

 This would allow for things like this:
  * `current_user_can( 'customize', 'theme', $stylesheet )`
  * `current_user_can( 'customize', 'post', $post_id )`

 At the moment, we should go with 'customize' with no additional arguments,
 I'm just showing the potential future usage.

 For now, 'customize' only refers to themes, so it would map to
 'edit_theme_options'. In the future, though, it might be used for a
 particular post. (At least in plugins for the foreseeable future.)

 I'd rather not add a new capability here as capabilities are not a great
 experience (custom roles don't get them automatically), and "customize"
 isn't very primitive — customizing *what* is the question, and to answer
 that question, we already have it in the form of edit_theme_options,
 edit_posts, etc.

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


More information about the wp-trac mailing list