WordPress角色自定义能力设置为true但返回false。

14

我尝试创建一个具有自定义功能的用户角色。目前为止,这个方案是有效的。但如果我想使用函数current_user_can()来检查某个特定功能的用户权限,它将返回false。但在新创建的角色的功能数组中,特定的功能被设置为true。

因此,为了让我的话更具编码背景:

角色对象

WP_Role {
  ["name"]=> "organizer"
  ["capabilities"]=> {
       ["edit_posts"]              => bool(false)
       ["delete_posts"]            => bool(false)
       ["publish_posts"]           => bool(false)
       ["upload_files"]            => bool(true)
       ["edit_event"]              => bool(true)
       ["read_event"]              => bool(true)
       ["delete_event"]            => bool(true)
       ["edit_events"]             => bool(true)
       ["edit_others_events"]      => bool(false)
       ["publish_events"]          => bool(false)
       ["read_private_events"]     => bool(true)
       ["read"]                    => bool(true)
       ["delete_events"]           => bool(true)
       ["delete_private_events"]   => bool(false)
       ["delete_published_events"] => bool(true)
       ["delete_others_events"]    => bool(false)
       ["edit_private_events"]     => bool(false)
       ["edit_published_events"]   => bool(true)
       ["manage_event_terms"]      => bool(true)
       ["edit_event_terms"]        => bool(true)
       ["delete_event_terms"]      => bool(true)
       ["assign_event_terms"]      => bool(true)
  }


我的添加角色功能

add_role( 'organizer', __( 'Organizer', 'eventtool' ), array(
            // General
            'edit_posts'              => false,
            'delete_posts'            => false,
            'publish_posts'           => false,
            'upload_files'            => true,
            'edit_event'              => true,
            'read_event'              => true,
            'delete_event'            => true,

            // Primitive capabilities used outside of map_meta_cap():
            'edit_events'             => true,
            'edit_others_events'      => false,
            'publish_events'          => false,
            'read_private_events'     => true,

            // Primitive capabilities used within map_meta_cap():
            'read'                    => true,
            'delete_events'           => true,
            'delete_private_events'   => false,
            'delete_published_events' => true,
            'delete_others_events'    => false,
            'edit_private_events'     => false,
            'edit_published_events'   => true,
            'edit_events'             => true,

            // Terms
            'manage_event_terms'      => true,
            'edit_event_terms'        => true,
            'delete_event_terms'      => true,
            'assign_event_terms'      => true
        )
);


自定义文章类型参数

register_post_type( 'event', array(
                'labels'              => $labels,
                'description'         => __( 'This is where you can add new events to your page.', 'eventtool' ),
                'public'              => true,
                'show_ui'             => true,
                'capability_type'     => 'event',
                'map_meta_cap'        => true,
                'publicly_queryable'  => true,
                'exclude_from_search' => false,
                'hierarchical'        => false,
                'rewrite'             => _x( 'event', 'slug', 'eventtool' ),
                'query_var'           => true,
                'supports'            => array( 'title', 'editor', 'excerpt', 'thumbnail' ),
                'show_in_nav_menus'   => true
            )
        );

【更新】
function et_modify_map_meta_cap( $caps, $cap, $user_id, $args ) {

    var_dump($cap)

}
add_filter( 'map_meta_cap', 'et_modify_map_meta_cap', 10, 4 );

输出“edit_post”,而不是“edit_event”



有什么建议,为什么会出现这种错误行为?


1
你没有展示你在哪里使用 current_user_can... 而且过滤器 map_meta_cap 和这有什么关系?我的 var_dump($cap) 显示了 edit_events - brasofilo
谢谢brasofilo。你的回复让我跳出了思维定势。 :) - kindisch
3个回答

1

今天我解决了它。

对于current_user_can()函数的第二个参数,赋予一个对象id是必要的,以获取单点能力(例如'edit_post')的正确返回。否则,如果未设置此参数,则该函数将返回false。

正如WordPress文档中所述:

如果省略,您可能会收到“Undefined offset: 0”警告(这是因为current_user_can函数最终调用map_meta_cap时,当检查元能力时,期望一个数组但只提供了一个单一的值)


0
尝试先将这些“capabilities”注册到自定义文章类型“event”,然后将这些“capabilities”分配给“organiser”。
像这样:
function create_my_post_types() {
    register_post_type(
        'movie',
        array(
            'public' => true,
            'capability_type' => 'movie',
            'capabilities' => array(
                'publish_posts' => 'publish_movies',
                'edit_posts' => 'edit_movies',
                'edit_others_posts' => 'edit_others_movies',
                'delete_posts' => 'delete_movies',
                'delete_others_posts' => 'delete_others_movies',
                'read_private_posts' => 'read_private_movies',
                'edit_post' => 'edit_movie',
                'delete_post' => 'delete_movie',
                'read_post' => 'read_movie',
            ),
        )
    );
}

将代码更改为event文章类型。

并使用以下代码检查用户权限:

add_filter( 'map_meta_cap', 'my_map_meta_cap', 10, 4 );

function my_map_meta_cap( $caps, $cap, $user_id, $args ) {

    /* If editing, deleting, or reading a movie, get the post and post type object. */
    if ( 'edit_movie' == $cap || 'delete_movie' == $cap || 'read_movie' == $cap ) {
        $post = get_post( $args[0] );
        $post_type = get_post_type_object( $post->post_type );

        /* Set an empty array for the caps. */
        $caps = array();
    }

    /* If editing a movie, assign the required capability. */
    if ( 'edit_movie' == $cap ) {
        if ( $user_id == $post->post_author )
            $caps[] = $post_type->cap->edit_posts;
        else
            $caps[] = $post_type->cap->edit_others_posts;
    }

    /* If deleting a movie, assign the required capability. */
    elseif ( 'delete_movie' == $cap ) {
        if ( $user_id == $post->post_author )
            $caps[] = $post_type->cap->delete_posts;
        else
            $caps[] = $post_type->cap->delete_others_posts;
    }

    /* If reading a private movie, assign the required capability. */
    elseif ( 'read_movie' == $cap ) {

        if ( 'private' != $post->post_status )
            $caps[] = 'read';
        elseif ( $user_id == $post->post_author )
            $caps[] = 'read';
        else
            $caps[] = $post_type->cap->read_private_posts;
    }

    /* Return the capabilities required by the user. */
    return $caps;
}

在这种情况下,为register_post_type函数分配额外的“capabilities”数组是不必要的。参数capability_type会为您完成此操作。例如,如果您有帖子类型“memory”,那么它是必需的。然后它将自动生成edit_others_memorys而不是edit_others_memories。因此,您可以在capabilities参数中进行调整。 - kindisch
那样做行不通。这些功能被设置为组织者并且在WordPress数据库中,所以无论我在register_post_type函数之前还是之后添加这些功能到角色中都没有关系。重要的是它们被设置在角色对象内部,并且已经设置好了。 - kindisch

0

这也会返回false,因为user_can()get_current_user_id()调用了同一个函数来检查能力。请参见此处,第501行return call_user_func_array( array( $user, 'has_cap' ), $args ); - kindisch
那么你有两种方法来实现它。首先,将WP_Role视为OOP对象,并检查“capabilities”属性数组中是否存在某个元素。或者你可以通过$wpdp查询进行检查。 - Loai Abdelhalim

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接