It’s working now. I’m not sure why or how. I tried applying the workaround to bug 19378 that’s posted in comment 6 of this page ( http://core.trac.wordpress.org/ticket/19378 ) since it looked related. It didn’t seem to have an effect immediately, but I am guessing that’s what did it?
Capability to read user’s own draft post of CPT
There is no right answer to this. You need to use the capability or capabilities that allow the users you want to have access to have access and prevent the users you don’t want to have access from having access. I would tend to create a capability and/or role in this kind of circumstance, but … Read more
Thanks brasofilo! add_action( ‘pre_get_posts’, ‘hide_pages_to_user_except_admins’ ); function hide_pages_to_user_except_admins( $query ) { if( !is_admin() ) return $query; global $pagenow; $pages = array(‘201′,’38’,’99’); //page ids if( ‘edit.php’ == $pagenow && ( get_query_var(‘post_type’) && ‘page’ == get_query_var(‘post_type’) ) ) $query->set( ‘post__not_in’, $pages ); return $query; }
As said in comment above is more easy remove the added capabilities. Below, as example, a simple implementation: class MyAwesomePlugin { static $capabilities = array(‘a_cap’=> true, ‘another_one’=> true, ‘third_cap’=> true); static $custom_roles = array(‘one_role’ => ‘One Role’, ‘second_role’ => ‘Second Role’); static $core_roles = array(‘administrator’, ‘editor’, ‘author’); static function install() { // add custom capabilities … Read more
I found the problem. There was a line of code that was deleting all posts as soon they were created. It may seems slly but it was wanted, I’m building a really custom app based on wordpress… Simply I forgot that this would cancel many other things that pods saves as post, like pods pages … Read more
You cannot assign capabilities to unknown users. If you want to make a post visible for everyone, create a separate URL for these posts and add a control element to the post editor to enable the preview on selected posts only. When such an URL is called, check if a preview is allowed for the … Read more
This issue has been solved by an update to the plugin by the developers after prompting by support tickets. The WP-Client plugin is currently at v3.5.1
Adapt the easier way. Install a plugin (Ex. Members) that can manage roles. Create one role with restricted access in your case a role with all the capabilities but not ‘create_users’, ‘add_user’, ‘list_users’,. Save this new role and assign it to the user you want to grant these restricted privileges.
You don’t need a special capability. When editing a post the editor just need to click on the tab “option” in the upper right corner and check the box for visibility of custom fields.