Posted by ladybug_3777 on July 31, 2012 at 1:06pm
3 followers
Jump to:
| Project: | IMCE Tools |
| Version: | 7.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I am only able to access the Directory Manager Configuration link if I am logged in a the Drupal SuperUser. Do I have something set up incorrectly or is this the way it is intended to work? I didn't see anything about having to be the superuser in the documentation.
Comments
#1
bump. Is anyone checking the issues on this module or is it dead?
#2
You should be able to access the configuration with any account that has "administer site settings" permissions. I've updated the README file to clarify this. Thanks for for pointing out the oversight.
#3
Hm... I feel kind of silly but I'm still having trouble with this! I have a user set up with the Administrator role. In Drupal 7 I see a setting on the Permissions screen for "Administer site configuration" and this is checked/turned on for the Administrator role. However my user still does not see the "Configure" option for Directory Manager.
I did not see a setting with the specific wording you mentioned of "administer site settings" on the Permissions screen. I'm a Drupal Newbie so maybe I'm looking in the wrong place? I am assuming the "Administer site configuration" option is what you meant, but since its not working I must be off base. Sorry if this is a stupid question!
#4
I should also add, my administrator role also has permission to "Administer IMCE". (If that matters at all)
#5
Looks like I had specified the required permission incorrectly and it should be 'administer site configuration' instead of 'administer site settings'. I've corrected this and am pushing out a new release with the fix (7.x-1.1). Also reclassifying this as a bug report from a support request. A cache clear should be all that is necessary to have the new permission picked up. Thanks for pointing out the error.
#6
Thank you tekante! I finally took a look at the .module file (I should've done that before!) and do see the issue now.
For anyone that wants a quick fix for this, prior to downloading the new version that will include the fix, you can simply change:
'access arguments' => array('administer site settings),To:
'access arguments' => array('administer site configuration'),I'm glad I reported it, but now I feel like I should've been able to easily find this bug on my own. DOH! Newbie fail! (but still learning! haha)
Thx again.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.