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

[WordPress Trac]

#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 dlh):

 Replying to [comment:4 westonruter]:
 > Another question: I see `capabilities` is now mapping meta caps to
 `edit_theme_options`. Just to confirm that is desired as opposed to
 introducing new primitives like `edit_customize_changeset` which are then
 added to the administrator?

 It was intentional, but I'm glad you brought it up. I've kept
 `edit_theme_options` so far primarily because of the concerns raised in
 ticket:36368#comment:5 about new primitive caps. Do you think we should
 try to use primitive caps along with, say, a `user_has_cap` filter to
 provide backwards-compatibility?

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