On a fresh Drupal 6.10 install, I have enabled Attribute, and added all the permissions to the Drupal Administrator Role, but Attribute doesn't show up in the Store Administration Menu. Also, when I try to access the path http://mysite.com/admin/store/attributes I get a Access Denied message and "You are not authorized to access this page." The other modules seem fine.

Thanks, Chris

CommentFileSizeAuthor
#2 Permissions | Screencast.jpg65.88 KBthill_
#2 Access denied | Screencast.jpg248.16 KBthill_

Comments

cha0s’s picture

cha0s commented
Assigned: Unassigned » cha0s
Status: Active » Postponed (maintainer needs more info)

Hm, I can see admin/store/attributes fine here on my local. Please double check your permissions settings and try again...

thill_’s picture

thill_ commented
Status: Postponed (maintainer needs more info) » Active
Issue tags: +permissions
StatusFileSize
new Access denied | Screencast.jpg248.16 KB
new Permissions | Screencast.jpg65.88 KB

cha0s,

I can confirm the issue, I created a role of store admin and only gave that role the three permissions under uc_attribute as shown in shot 1, then as that user i tried to go to the admin/store/attributes and you will see the denial in shot 2.

cha0s’s picture

cha0s commented
Status: Active » Postponed (maintainer needs more info)

Sorry, I can't reproduce it. I'm thinking you might need to truncate your cache_menu table (or use a module like devel to clear your cache) since access stuff changed there. I created a role on a user with administer attributes permission and I can access admin/stor/attributes no problem.

cha0s’s picture

cha0s commented

Well, this bug is because of a typo that was in uc_attribute at the time of the last beta.

You can get a patch for 2.x here: http://drupal.org/node/279611#comment-1310184 that fixes the typo and also updates your permissions table to correct the issue.

cha0s’s picture

cha0s commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

Marking as duplicate.

kevinquillen’s picture

kevinquillen commented

Thanks, this definitely does correct the issue.

Can't believe the first thing I thought to do was look at hook_perm, and totally didn't see the typo. Cest la vie.