I have a global flag applied to my content type "location". Only user/1 can use the flags. Whether configured as javascript or regular link all roles get a 403 access denied error "you are not authorized to access this page" when clicking the flag. When they click the error shows with the URL of the flag link. For example:
mysite.com/flag/unflag/flagname/19?destination=node%2F19token=8b7ad88a3dd98909320934302974
I don't have any other permissions modules installed. All the roles appear to be configured correctly.
Even if given the administer flags permission the roles are still not able to use the flags. All the roles have access to view and edit the "location" type and all the fields within it.
At one point I changed the name of the flag. I thought this might be the cause so I created a new flag and the same thing is happening with the new flag, too.
Recommendations for other tests are welcome. Thank you!
Comments
Comment #1
discursives commentedI see that perhaps I wasn't clear. All roles have access to use the flag, but every role and user besides user 1 gets the error when they attempt to use the flag.
Comment #2
quicksketchHave you granted users the "access content" permission? It looks like Flag ties access to the menu callback to that permissions (under the assumption that all users would have access to content).
Comment #3
quicksketchHm, well marking fixed unless I get a response back.
Comment #5
vishy_singhal commentedI am getting a similar error.
I have a role created - XYZ and have assigned the role the permission to flag a content. But when I execute a user having role XYZ, it shows 403 error
Comment #6
vishy_singhal commentedComment #7
joachim commentedWhat link type are you using? Have you tried this with uid 1? Does the role have the 'access content' permission?
Can you try this with 3.x?
Comment #8
vishy_singhal commentedIs 3.x production ready?
Comment #9
joachim commentedYes, though as always, try the upgrade process on a development copy first.
Though for the purposes of testing this bug -- try it on a dev copy anyway!
Comment #10
vishy_singhal commentedThere were permission issues. I fixed them all. Please go ahead and close this defect.
Comment #11
joachim commentedThanks for reporting back!