WordPress 4.7 introduces new capabilities for individual taxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. terms, allowing developers to implement more fine grained control over management of terms (including categories, tags, and custom taxonomy terms). The new capabilities are meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. capabilities that ultimately map back to existing capabilities, so there is no change in behaviour for existing functionality and users.
New Singular Capabilities
edit_termdelete_termassign_term
In the same way that capabilities such as edit_post and delete_user are used to check that a user can perform the action for a specific post or user, these new capabilities can be used to check that a user can perform the action for a specific term. If you’re currently checking the edit_terms, delete_terms, and assign_terms capabilities, you can switch these over to the singular form and include the term ID as the second parameter. Example:
if ( current_user_can( 'edit_term', $term_id ) ) {
printf( '<a href="%s">Edit This</a>', get_edit_term_link( $term_id ) );
}
The new capabilities are meta capabilities — which means they ultimately map back to the existing manage_categories capability by default, or whichever capability has been specified in the corresponding capability arguments when registering the taxonomy. The actual required capabilities can be filtered using the map_meta_cap filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. like so:
add_filter( 'map_meta_cap', function( $required_caps, $cap, $user_id, $args ) {
switch ( $cap ) {
case 'delete_term':
$term_id = $args[0];
// Prevent a "protected" term from being deleted:
if ( get_term_meta( $term_id, 'protected', true ) ) {
$required_caps[] = 'do_not_allow';
}
break;
case 'edit_term':
// Introduce some anarchy:
if ( rand( 1, 6 ) == 3 ) {
$required_caps[] = 'do_not_allow';
}
break;
}
return $required_caps;
}, 10, 4 );
Separate Capabilities for Tags and Categories
A related change is that the post tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) taxonomy now uses separate capabilities from the category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. taxonomy by default (it previously used the same capabilities as the category taxonomy). This doesn’t alter existing behaviour (custom or otherwise), but it does mean that you can target capabilities for tags separately from categories. Example:
add_filter( 'map_meta_cap', function( $required_caps, $cap, $user_id, $args ) {
switch ( $cap ) {
case 'manage_post_tags':
case 'edit_post_tags':
case 'delete_post_tags':
case 'assign_post_tags':
// Allow Authors to manage tags:
$required_caps = array(
'publish_posts',
);
break;
}
return $required_caps;
}, 10, 4 );
See Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket Created for both bug reports and feature development on the bug tracker. #35614 for more information.
#4-7, #dev-notes
