Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I've been debugging a very screwy issue with the Workflow module in which the $user->roles array is getting returned as key=>rid rather than rid=>role title, as should be the case. I traced this bug through about a half million functions before finding myself at project_issue_views_user_access(). Specifically, line 1695, which reads:
$arg_uid = $view->argument[$argument_name]->get_value();
The $user object is fine on one side of this line, and is altered on the other side. This breaks Workflow, of course. I was pretty tired of digging by this point, and we decided the easiest solution for us would be to simply disable the Project module and reproduce the functionality we needed in another way.
This appears to happen only on node forms, though I can't swear to that. It seems to be related to the access check for the My Issues menu item, and the argument_name is uid_touch. We're also using OG, so it might be some combination of all three modules which is causing this.
Comments
Comment #1
phl3tch commentedAn addendum. I figured out that I could make this go away by disabling the project_issue_user_projects view. So, there must be something awry in there.
Comment #2
phl3tch commentedSorry to dribble this in like this, but the view project_issue_user_issues also appears to be a culprit.
Comment #3
dwwSorry, but this makes absolutely no sense. ;) That function is not touching the $user object at all. I don't see how this is a bug in project_issue...
Can you provide some very specific details on how to reproduce this bug on a clean installation with the smallest # of modules enabled? Otherwise, I can't really help you here.
-Derek
p.s. I just looked through some code in views. Can you try turning off the user validation on the user argument in the views and see if that changes the behavior? It's possible that views_plugin_argument_validate_user.inc is the thing breaking the $user object, although even then, that's hard to believe.
Comment #3.0
dwwUnpublishing since it looks like this might be a security bug in views.
Comment #4
dwwYeah, upon closer inspection, this is definitely your problem:
#832954: global $user->roles get changed by argument_user_validate
Comment #5
phl3tch commentedYeah, it's weird, but we've moved on. It had something to do with the Project module. We didn't need that module that much, so we got rid of it and everything works fine now.
Comment #6
dww@CrackWilding: You misunderstand comment #4. There was no bug in Project module. The bug was in views, and is now fixed.
Comment #7
phl3tch commentedOh, oops. And thanks.