I am trying to:
Create a new role will limited permissions
I visited this URL:
I expected to see:
User permissions effective.
Instead, I got:
Log in as limited role user and edit permissions not effected correctly - specifically, user could not edit the Types CPT posts, regardless of how permissive I set the permissions in both the role setup and the CPT screen in Access.
Rolled back to previous release (v2.3.1) and it functions as expected.
Hi, as a test could you try the following steps:
- Update to 2.4
- Log in as custom role user
- Create and publish a new post in your custom post type
- Return to CPT dashboard and review edit capabilities for own post and others posts
Does publishing a post in your CPT make any difference?
Sorry I'm not sure I understood your last comment, did you mean that you are unable to create a post right now because it's not possible in the wp-admin area when you are logged in as your custom user role, or are you unable to create a post right now because it's not a good time to make changes on your live site?
Either way, it might be best for me to run some tests on a clone of your site so I can make changes without breaking anything live. If that's okay with you, please provide login credentials for me in the private reply fields enabled here. I will install the Duplicator plugin (https://wordpress.org/plugins/duplicator), create a clone, install it locally and begin testing. Please include login credentials for both an admin and a custom user role user.
Once I installed your site clone, I was able to resolve this by taking the following steps:
- Go to Toolset > Access Control > Custom Roles. Click "Change Permissions" underneath the Adventure Admin role (I assume this is the custom role in question). I see that 8, 9, and 10 are currently unchecked. Please check these.
- Ensure that the custom role has no Publish permissions for any custom post type in question. It looks like this is currently set up correctly in Toolset > Access Control > Post Types > Adventures, but not in all custom post types. Please set this appropriately for all CPTs.
- Set a user as Adventure Admin role, and log in to verify this is working as expected.
Please let me know if these steps do not work for you and I'll take another look.
Try now - I privately published a test post by the aejv-care user, then deleted it. When I was testing on my own local environment, I found that publishing a post, even privately, by the Adventure Admin in question seemed to open up their edit access. Can you confirm this works for you? If so, I will escalate this situation to our developers as a potential bug.
Note that publishing a post "privately" hides it from the public - only Administrators and Editors will be able to see it.
Followed your steps as the aejv-care user. Did not have option to create a Private post. So submitted it for review. Checked other posts, still not able to edit.
Logged in as admin user, changed aejv-care user post to Private & published. Reverted to aejv-care user and updated the post. It was changed to a Public post and "Submit for Review". Still cannot edit.
Created new post, saved as draft. Still cannot edit other posts.
See attached screenshots with timestamps.
It's still a dev site, so feel free to experiment.
As Christian is currently unavailable i'll be handling this ticket for you.
I was able to verify this issue that whenever the user doesn't have Publish Permissions on the post then they won't be able to edit their posts because edits I believe require publish permissions.
Setting the role to have publish permissions allows the user role to work correctly. Is their any reason why the Adventurer admin wouldn't be able to publish posts of the Adventure CPT ?
The end goal is to have the aejv-care user configured with the ability to create and edit/update Adventure CPT posts, but not be able to publish any posts regardless of who created the post (they can submit the new/edited posts for review).
As it stands this user can create new and edit their own posts, but cannot edit existing posts. This is the issue I need resolved.