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.
It would be great if the module could use its own permissions instead using the general 'administer block'.
Comment | File | Size | Author |
---|---|---|---|
#6 | on_the_web-permissions-2557095-6.patch | 889 bytes | ckrina |
Comments
Comment #2
ckrinaHere is a small patch proposal to change it.
Comment #3
ckrinaComment #4
ckrinaIt would be great to have an update function to give this new permission to all the previous roles with access to to the form, but my knowledge is not good enough to write it.
Comment #5
rodrigoaguileraYeah, I think it makes sense to have a separate permission.
The header comments should be Implements hook_blabla acording to the coding standars
Still needs a hook_update_N function to grant the new permission to all the roles that had the "administer block" permission
Comment #6
ckrinaUpdated patch with #5 comment.
Update function still needed.
Comment #7
jenlamptonGood idea :)
There are two settings forms, the one on the block as well as the one on it's own page. You'll need to update the block configuration form to use this new permission too, otherwise there's no point in having this permission (as you can override them all per-block anyway).