I am trying to:
Allow a single user, which is a "contributor", and cannot be more than that, to be able to have full rights, including editing / deleting / publishing a custom post type created with types.
I allowed this user full control on the custom post type on the access admin area.
This user is able to edit the custom post type, except when the post is published.
What should I do ?
Thanks a lot
Charles
I set up a quick local test according to your elaborated details.
1. A Post Type made with Toolset Types (it's all native default settings)
2. A User, of role "Contributor".
3. In Toolset Access > Post Types > my_custom_post_type I gave all the rights to this one user only.
I attached some screenshots that show how to do that.
Then, I logged in as this Contributor User and added new Posts in my Custom Post Type.
I edited them, deleted them, previewed them, edited after publishing...
This all works fine unless one thing:
The Preview.
That is a known BUG:
https://toolset.com/forums/topic/cannot-preview-changes-to-existing-posts-with-access-plugin-enables/
So far, it all works fine for me on the Latest Toolset Plugins, with no other SoftWare on the site.
Could you confirm that your settings are alike mine?
Hello Beda and thanks for your answer during the weekend !
OK all these things work for me too. Trouble begins when I try to edit a post published by another user.
My contributor, having all the rights on that CPT, should have the right to edit / delete another user's post of this CPT. How would I do ?
Thanks a lot !
Charles
You are right.
Not even the global settings work in this case.
Only when you bring native Posts under the same type of control, then it works.
Of course, I chose to "Managed by Access" for my Custom Type.
I reported this as a BUG and will start debugging it so to bring it up to the DEV.
Thank you for the heads up.
Hello Beda !
Thanks for the precisions, and thanks for reporting it.
Does this mean that if I change a setting ont he native Post post type for this user, it will then work for the cpt ?
Thanks a lot
Charles
Dear Beda,
I think I managed to find the solution, and that's because of you!
I gave the user "Joe" special right for native Posts. And now the rights are ok for the cpt and for the posts. (first two screenshots).
And then I deleted the special rights for this user (screenshot 3.png), and it still works OK !
Weird, but well, it works as it should... There certainly must be a reason.
Please keep me updated when this bug is resolved. Should I mark this issue as "resolved" ?
Thanks a lot
Charles
Hello Beda,
unfortunately, this setting does not seem to work on the long-term. Removing the rights on native Posts removes them too on CPT.
The problem is I don't want the user to have rights on native posts, only on some CPT.
I saw that giving all rights on native Posts gives rights on all post types. That's annoying.
Thanks for keeping me updated.
Charles
I observed a strange behaviour on children cpt. Are the rights on this cpt dependant from their father's ?
Hello Beda, Perhaps I should use another ticket, but I have an issue on this peculiar problem (perhaps more linked to wp-types than wp-access) :
As an editor, I cannot edit custom some post type created by another. All the CPT I've created behave corrrectly, except for this one.
The only difference I can think of is this CPT being a child type of two other CPT.
What do you say ?
Charles
Here is a screenshot of this CPT's config
Looking forward to having news from you,
Charles
I'm sorry to not have followed up here.
The Fix is planned for Toolset Access 2.5, and the solution (workaround) is as Noman pointed out in the other ticket.
Thank you for the patience.
Meanwhile we published an Erratum for this issue:
https://toolset.com/errata/contributors-have-no-edit-permission-on-others-custom-post-types/
There is a workaround.
Thank you for the patience.
There is a workaround in the erratum, and it will be updated as soon there are better solutions.
https://toolset.com/errata/contributors-have-no-edit-permission-on-others-custom-post-types/
Hence I close this ticket here.
