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 just tried this module for the first time and noticed that unauthorized users can also make changes to the fields. Is there a way to restrict editing only to the particular role based on the basic drupal access permissions. I'd want to avoid using Field Access module, since it's going to add more unnecessary complexity.
Comments
Comment #1
joachim CreditAttribution: joachim commentedYou can set a permission on the whole view.
Comment #2
pedas126 CreditAttribution: pedas126 commentedHi Joachim,
Could you explain how to set this, i am new drupal user, i had try to set the permission, but only could see edit ,delete the content type permission but not view permission.
Expected result would be: Anonymous and authenticated user could only view the content, while administrator only could edit the content.
Thanks alot,
adam
Comment #3
joachim CreditAttribution: joachim commentedWhat I mean is that you can edit the View, and set access control for the entire View.
> Expected result would be: Anonymous and authenticated user could only view the content, while administrator only could edit the content.
That's rather more complicated. We'd need the edit handlers to have code to check access, which would be a new feature.
That's not something I'm likely to look into as part of my projects, as we use access control on the whole view. If you want this feature, you'll have to get it developed and provide a patch, I'm afraid.
Comment #4
W.M. CreditAttribution: W.M. commentedI also think that a special permission should be available that would restrict, if desired, the ability to edit nodes via Editable Views independent whether a particular role is able to view the view or not.
Moreover and preferably, if there is no permission to use Editable Views for a particular role, then the Editable View's fields and Save button should not be rendered for that role at all.
Thanks.
Comment #5
Ether CreditAttribution: Ether as a volunteer commentedTo bad. Unfortunately I cannot use this module without right restriction on field level. Any suggestions for the similar project ?
Comment #6
joachim CreditAttribution: joachim commented> I'd want to avoid using Field Access module, since it's going to add more unnecessary complexity.
Despite the extra complexity, the logical thing would be to use Field Access module. It might work OOTB -- can someone try it?
Comment #7
Ether CreditAttribution: Ether as a volunteer commentedLooks like the module works well with Field Access. Thanks.
Comment #8
joachim CreditAttribution: joachim commentedGreat! Thanks for reporting back.
I'm going to change this to a support request and close it. Field Access is an established solution for per-field permissions, so it makes sense to use that rather than implement a whole new system for that.