Problem/Motivation
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.
Steps to reproduce
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.
What should happen
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.
What actually happens
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.
Proposed resolution
The access section rule should limit adding content to specific menu items, not blanket disallow posting that type of content.
Remaining tasks
Work out the best solution to allow this.
Implement the changes.
User interface changes
TBC
API changes
TBC
Data model changes
TBC