Closed (fixed)
Project:
Workbench
Version:
7.x-1.2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Oct 2012 at 12:31 UTC
Updated:
25 Feb 2013 at 21:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
mrfelton commentedComment #2
devin carlson commentedThe patch applied cleanly and fixed the configuration section using the wrong permission.
Comment #3
agentrickardCommitted.
Comment #4
mrfelton commentedps, thanks for the (lack of) patch attribution! ;)
Comment #6
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 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 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.