@phloo Can you take a look at the Capabilities screen and let me know whether you’ve enabled Type-Specific Capabilities for those custom post types? If so, you’ll need to assign the corresponding capabilities to the Editor role (mirroring Post capabilities the Editor role already has).
Thread Starter
phloo
(@phloo)
Hi Kevin. I had no idea what Capabilities screen you mean, and then I saw I posted on the wrong support forum.
I was refering to the Permissions plugin, not the capabilities.
Any idea why this happens as soon as I activate it?
Thread Starter
phloo
(@phloo)
PS: the CPT is not set for the type-specific capabilities. And it s not about editing. Its about viewing those pages on the frontend.
It may actually be a similar issue. Take a look at Permissions > Settings > Core > Filtered Post Types. Are your custom types enabled there? If so, the Editor role will need the corresponding capabilities (mirroring Post capabilities already assigned).
Thread Starter
phloo
(@phloo)
Checked. Not activated for those kind of posts.
I still dont understand why reading posts is a permission thing.
Sorry, our responses crossed. Since CPT implementations can be custom, the editing cpabilities could be in play on the front end. It’s a first pass check I need to eliminate, anyhow.
Have you configured any other Permissions settings related to these post types?
How are the custom types registered? If you have your own register_post_type() call, please share. If you prefer, we can pick this up through a help ticket at publishpress.com
Thread Starter
phloo
(@phloo)
That would be helpful. Here? https://publishpress.com/free-support/
And yes, I register the CPT via the WP functions.
Yes, that’s the right form.
@phloo Can you confirm this was resolved? I don’t see your support ticket in our system.
Thread Starter
phloo
(@phloo)
Has not been resolved. Your support asked me to become a paid member to receive help on this. We declined (cause paying for something that never worked for us from the start is a nogo)
