[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 westonruter):

 @dlh I think your first approach is ideal. It would give the maximum
 flexibility for plugins to filter `map_meta_cap` to manage whether a user
 can publish a specific post that has been created, or if the post hasn't
 been created yet to publish posts of that type generally. Right?

 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? I suppose in that case it lies in the realm of
 plugins to supply a different primitive capability if they're wanting, as
 in the case of Customize Snapshots, to optionally restrict publishing
 changesets for specific roles?

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