Helen Hou-Sandi

The latest version fixes those problems – I suppose some Role Scoper settings must still have been in effect even after disabling the plugin. Thank you for that!

However, now the pages tree view under Pages shows posts.

This has to do with meta capability mapping. See more at https://www.ads-software.com/support/topic/custom-post-type-only-working-when-logged-in

Edit/update: I figured it out soon after posting this! It turns out that it has to do with meta capabilities not being automatically mapped. See: https://justintadlock.com/archives/2010/07/10/meta-capabilities-for-custom-post-types

Basically, you should define the capabilities array and give your custom post type its own capability_type. It may work to use the same capability_type/capabilities for multiple custom post types, but I haven’t tried that yet.

Also, I am using Role Scoper, so I did not need to do the actual mapping of capabilities. The latest beta of Role Scoper works with CPTs.

———————————–

I’m having exactly the same problem and so far haven’t figured out what’s going on. I do see a custom post type item in my database though, along with revisions and a trashed item. I wonder if it has to do with the capability_type or assigned roles?

Maybe we can help each other – are you using the multisite feature? Plugins?

Update: It looks like this behavior is actually on all of my multisite blogs. Is this related to the multisite feature?

I think that could be useful, but I think the behavior for a person with a scoped role is actually correct – it only shows pages for which they have editing permission. However, since an editor should have editing permission for all pages on a site, the page tree view should show for them, but right now all it shows is an empty tree.

Having the same problem here as well. Oddly enough, CMS Page Tree View will show pages with scoped permissions (via Role Scope) for somebody who is not an editor.

You are really and truly fantastic. As far as I can tell for the moment, everything I need is working perfectly! Your plugin is the backbone of justification for my current WP-as-CMS project, and I can’t thank you enough for the work that you do. I’ll keep an eye out for any other funky occurrences, but for now, thank you!

Yes, this is fixed for site_wide options in beta 4! This is great – thank you so much.

Now, when I set a user to have a role (i.e. be an editor) for a specific post of a custom type (a faculty member, in my case), the custom post type does not show in the admin menu, although the user can indeed update the post itself when the URL for the post to edit is navigated to. If I set the user to only be an editor for a page, however, the page menu does show up. Is there something I need to set in order for the custom post type admin menu to appear?

Well, I did some more investigating and it looks like no options under Realm save for me, although options under other tabs are. I will try deactivating other plugins to see if there is a conflict out there and report back. Where/how are these options saved?

Update: Tried deactivating all plugins and removing all functions except initializing the custom post type, but options were still not saved. This is crucial to our site development – any other ideas?

I did make sure to set the priority to 1, but still not working for me. Any other reason it wouldn’t save the checkbox selection?

I’m having the same issue with not being able to save my checkbox selection in front of a custom post type. jli – did you do anything specific to get it working?

I found the same thing as well. You should change line 243 as well if you change line 244, as that controls the state of the text when it’s not a link.

So:

Line 243:
if ($allpage_link) $output .= '<span class="contentjumpall"
becomes
if ($allpage_link) $output .= ' <span class="contentjumpall"

Line 244:
else $output .= '<a class="contentjumpall
becomes
else $output .= ' <a class="contentjumpall