[wp-trac] [WordPress Trac] #40922: Use finer-grained capabilities with `customize_changeset` post type

WordPress Trac noreply at wordpress.org
Tue Jun 20 22:47:05 UTC 2017


#40922: Use finer-grained capabilities with `customize_changeset` post type
-------------------------+------------------
 Reporter:  dlh          |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  4.9
Component:  Customize    |     Version:  4.7
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------

Comment (by westonruter):

 @dlh ok, good point. Yeah, re-using the existing primitive cap
 `edit_theme_options` is probably the right. But, will not switching to not
 use the `customize` meta cap cause problems for plugins (like Customize
 Posts) that grant the `customize` cap to allow users to access the
 Customizer to edit posts there? Since those users don't have
 `edit_theme_options` would they not be prevented from being able to make
 any changes? Wouldn't that mean that granting `customize` capability then
 no longer be sufficient to grant effective access?

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


More information about the wp-trac mailing list