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 would have thought access to /admin/config/workbench should use the 'administer workbench' permission instead of 'access workbench'. The 'administer workbench' permission isn't actually used anywhere in workbench (or any of the workbench add on modules that we have enabled). As it is now, content editors (or anyone with the ability to access the workbench) can also acess the admin page at /admin/config/workbench - which just shows "You do not have any administrative items.", which is confusing.
Comment | File | Size | Author |
---|---|---|---|
#6 | workbanch-permissions.png | 42.53 KB | sardbaba |
#1 | 1803198-workbench-admin-permissions.patch | 523 bytes | mrfelton |
Comments
Comment #1
mrfelton CreditAttribution: mrfelton commentedComment #2
Devin Carlson CreditAttribution: Devin Carlson commentedThe patch applied cleanly and fixed the configuration section using the wrong permission.
Comment #3
agentrickardCommitted.
Comment #4
mrfelton CreditAttribution: mrfelton commentedps, thanks for the (lack of) patch attribution! ;)
Comment #6
sardbaba CreditAttribution: sardbaba commentedIn workbench.module (7.x-1.2 version) I see this (as #1):
but is not working for me, as administrator.
I dunno why this isn't working. Any idea?
Comment #7
agentrickardHave you cleared the cache / run update.php?
By "administrator" do you mean user 1?
Comment #8
sardbaba CreditAttribution: sardbaba commentedYep, both cache cleared and I ran update.php.
And, yes, by "administrator" I mean user 1, of course :)
Comment #9
agentrickardDo you have any of the submodules enabled (Workbench Moderation, Workbench Access)? If not, this item won't appear because Workbench itself has no configuration.
Comment #10
sardbaba CreditAttribution: sardbaba commentedOh sh**! Sorry :)
Anyway, there is a usability problem in this: if you give the ability to access to a configuration page, but the configuration page doesn't have any configurations is better to follow one of the next options:
1) the configuration page has no sense to exists;
2) if you need to have the configuration page, is better display a message like "There aren't configurations at the moment" instead of an access error message.
Comment #11
agentrickardBlame core's handling of configuration blocks. This works as designed.