[Resolved] Need custom role to edit/create custom post, WooCommerce interference?

[Author]

Posts

[davidM-41]

On the subject website (www.SilverClefMusic.com) I have created a custom post type called "Program Notes." This works fine when I log in as Admin. This site is an ecommerce site with WooCommerce installed and operational.

I have created a custom role "Program Notes Editor" that I want to be able to assign to specific registrants to allow them to create and edit Program Notes CPT entries. I am pretty sure I have given this role and the CPT all the necessary permissions in Access.

However, when I log in as user "testeditor" with the role of "Program Notes Editor," the only screen I can see seems to be a WooCommerce screen that will not allow this role to create or edit a Program Notes CPT. See the screenshot for what the role user sees when logging in.

Any help you can offer to make this work will be very much appreciated.

[Minesh]

Hello. Thank you for contacting the Toolset support.

Well - you are aim to allow the user "testeditor" to edit the "Program Notes." on frontend or backend?

[davidM-41]

I need them mostly to be able to create new "Program Notes" postings, although they should be able to edit existing postings as well.

Either front end or back end would be fine, as long as they can do those two tasks.

Thank you.

[davidM-41]

UPDATE!

I have solved my issue by studying CRED and creating a form for adding new posts to the CPT, then using ACCESS to restrict access to that form to Admin and the custom role. I then put a link to the page with the embedded form on a relevant page, and used ACCESS to restrict visibility of the <div> with that link to only Admin and Program Notes Editor roles.

I've tested it quite a bit, and it seems to be working as it should.

This solved the underlying goal during which I encountered the problem mentioned in this thread. HOWEVER, it did NOT solve the issue of how can I get someone with a custom role to be able to see their WP Dashboard instead of what looks like the WooCommerce summary? That issue remains unsolved, even though it is no longer critical to the goal I needed to accomplish.

For that reason, I am leaving the issue "unsolved," although we can call it solved if you think that's better.

[Minesh]

Gald to know that you found a way to resolve your issue. Yes, kindly mark it resolved and open a new ticket for your each new question.

[davidM-41]

Issue is resolved.