Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #2
jygastaud CreditAttribution: jygastaud commentedThanks for reporting.
Will try to investigate that issue.
Comment #3
jygastaud CreditAttribution: jygastaud commentedSame 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 ?
Comment #4
jygastaud CreditAttribution: jygastaud commentedSorry 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.
Comment #5
Micha1111 CreditAttribution: Micha1111 commentedBecause 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.