Opened 3 years ago
Closed 2 years ago
#15437 closed defect (bug) (fixed)
Custom Post Type's capability_type and taxonomies used with the post type not considered when calling admin-ajax.php
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 3.1 |
| Component: | Administration | Version: | 3.1 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | admin@… |
Description
For ajax-tag-search and get-tagcloud in admin-ajax.php, the custom post type with custom capability_type and taxonomies set to use with the post type is never considered as !current_user_can( 'edit_posts' ) is hard coded. For example, a custom post type MY_CPT with custom capability_type CPT allows users to have the capability edit_CPTs. A user who cannot edit_posts, but can edit_CPTs will see -1 when editing a MY_CPT post tags, if post_tags is in the array of taxonomies used with the post type.
Attachments (1)
Change History (9)
- Keywords has-patch added; capability_type post_type admin-ajax get-tagcloud ajax-tag-search removed
- Severity changed from critical to normal
Patch.
- Resolution set to fixed
- Status changed from accepted to closed
Yes, assign_terms is the proper cap. I have tested and am changing to fixed. Thank you, Andrew!
Note: See
TracTickets for help on using
tickets.
It should go off of the taxonomy caps, I'd imagine.