Permissions are a bit messed up.
vegeneric - July 2, 2007 - 17:14
| Project: | Views Actions Links |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
on line 104: if(user_access(_views_actions_links_get_perm($action))) {
$action is going to be something like 'Action Name'; which is a valid permission.
on line 35: $access = user_access(_views_actions_links_get_perm(arg(2)));
arg(2) will be passed as 'action_name' and no user will ever have that permission because it doesn't exist.
The module will only work for Admin account.
#1
Why would arg(2) be passed as 'action_name'?
#2
Sorry that shouldn't be in there but that wasn't the point of the post. The module as it exists ONLY functions properly for account 1, a.k.a. the administrator. It looks like a problem with 'action_name' being passed as a permission instead of 'Action Name'.
#3
I just did a full text search of the .module file, and do not turn up a single match to the string "action_name". Can you explain where you see this coming from?
#4
Vegeneric,
Thanks for the heads-up. I was able to locate the problem, and it should be fixed in the 5.x-1.1 release.
#5
Marking fixed.
#6
no problem, thanks for the quick fix on that.
#7