In a situation where some content types can be posted to some of the available menus, it is easy to set up a situation where users cannot post any content even though the intention is that they should.
Create multiple content types, e.g. "Page", "Event", "News".
Create multiple menus, e.g. "Main menu", "Sidebar".
Enable some of the content types to be posted to the menus, e.g. "Page" can be posted to the "Main menu" and "Sidebar", "Event' doesn't allow posting to any menus.
Grant the "Authenticated user" permission to create all three types of content.
Create a Workbench Access access scheme on the "Main menu" menu that's tied to the "Page" content type.
Create a separate access scheme on the "Sidebar" menu that's tied to the "News" content types.
Add menu items to the two menus.
Add a specific user to one of the menu items in the "Main menu" access scheme.
Do not any users to the "Sidebar" access scheme.
The user should be able to create an "Event" node without restriction.
The user should be able to create a "Page" node and post it to the "Main menu" section(s) they were granted access to.
The user should be able to create a "News" node but not add a menu item.
User cannot create any content.
Loading /node/add or /node/add/event or /node/add/page gives a 403.
The "Content" menu doesn't show the "Add content" item.
The access section rule should limit adding content to specific menu items, not blanket disallow posting that type of content.
Work out the best solution to allow this.
Implement the changes.
TBC
TBC
TBC
Needs work
2.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think the issue mentioned by yuehua in #12 above is fixed by 🐛 EntityCreateAnyAccessCheck::access() wrongly forbids access when the first bundle forbids access Fixed , which was released in Drupal 10.1.0 and 9.5.10 last month. (I don't know if that affects the original issue at all.)