I am trying to find the right setup for following usecase:

Authenticated users (or other roles) are only allowed to edit child nodes, but not to create new or delete existing child nodes.
So I checked the permissions on people/permissions :
Allowed to see add and edit buttons checked
Certain Content Type (Child nodes): Edit any Content checked (all other edit own, create and delete not checked)

If a user with this role go to node add/edit parent form, both buttons (edit and add) are not shown, although the user has permission to edit child nodes.

Comments

Micha1111 created an issue.

jygastaud’s picture

Thanks for reporting.

Will try to investigate that issue.

jygastaud’s picture

Same question here that in #2560875.
Why did you allowed users to see the add button if they are not the right to used it at all ?

jygastaud’s picture

Sorry I misread your comment.

Are you sure that your field instance allowed buttons to be displayed ? By default, if you haven't change it in administration form, buttons will not be displayed.

Micha1111’s picture

Because there is another content type where the same userrole is allowed to create child nodes
(different settings for different content types)
Yes, I am sure, entity connect settings in field settings form are ok.