我想知道是否可以以某种方式设置用户角色，即某些组中的用户只能编辑分配了特定分类法的帖子，例如：

Properties (Post Type)
    Taxonomy One
    Taxonomy Two
    Taxonomy Three

User Roles
    Group One - Can only edit properties with \'Taxonomy One\' assigned.
    Group Two - Can only edit properties with \'Taxonomy Two\' assigned.
    Group Three - Can only edit properties with \'Taxonomy Three\' assigned.

我正在使用Members plugin 对于目前的角色管理，我正在使用自定义的帖子类型/分类法。

从我目前所看到的情况来看，您似乎无法根据分类法限制对帖子的访问。

UPDATE

现在，我已获得使用以下代码处理帖子类型的权限：

register_post_type( \'properties\',
    array(
        \'labels\' => array(
            \'name\' => __( \'Properties\' ),
            \'singular_name\' => __( \'Property\' )
        ),
        \'public\' => true,
        \'capability_type\' => \'property\',
        \'map_meta_cap\' => true,
        \'capabilities\' => array(
            \'publish_posts\' => \'publish_properties\', // This allows a user to publish a property.
            \'edit_posts\' => \'edit_properties\', // Allows editing of the user’s own properties but does not grant publishing permission.
            \'edit_others_posts\' => \'edit_others_properties\', // Allows the user to edit everyone else’s properties but not publish.
            \'delete_posts\' => \'delete_properties\', // Grants the ability to delete properties written by that user but not others’ properties.
            \'delete_others_posts\' => \'delete_others_properties\', // Capability to edit properties written by other users.
            \'read_private_posts\' => \'read_private_properties\', // Allows users to read private properties.
            \'edit_post\' => \'edit_property\', // Meta capability assigned by WordPress. Do not give to any role.
            \'delete_post\' => \'delete_property\', // Meta capability assigned by WordPress. Do not give to any role.
            \'read_post\' => \'read_property\', // Meta capability assigned by WordPress. Do not give to any role.
        )
    )
);

编辑“成员”插件中的角色时，会出现“属性”部分，允许我限制/允许访问。现在只需要弄清楚这是否适用于每个分类法：）

    /**
     * Dynamically filter a user\'s capabilities.
     *
     * @since 2.0.0
     * @since 3.7.0 Added the user object.
     *
     * @param array   $allcaps An array of all the user\'s capabilities.
     * @param array   $caps    Actual capabilities for meta capability.
     * @param array   $args    Optional parameters passed to has_cap(), typically object ID.
     * @param WP_User $user    The user object.
     */
    $capabilities = apply_filters( \'user_has_cap\', $this->allcaps, $caps, $args, $this );

add_filter(\'user_has_cap\',\'check_post_taxonomy\',10,4);
function check_post_taxonomy($allcaps,$caps,$args,$user) {
    global $post; if (!isset($post)) {return $allcaps;}

    $group = get_user_meta($user->ID,\'special_edit_group\',true);
    $taxonomy = \'taxonomy_\'.$group; // maybe set to a, b or c?
    $terms = get_the_terms($post->ID,$taxonomy);

    // if there are no terms, remove the user capability(s) for this check
    // you may have to experiment to remove all the ones you want to
    if (!$terms) {
        unset($allcaps[\'edit_properties\']);
    }

    return $allcaps;
}