I've got a bit of an issue with Contextual filters in views showing the following errors after a D6 -> D7 upgrade:
Notice: Undefined index: restrict_roles in options_form() (line 40 of /home/user/public_html/sites/all/modules/contrib/views/modules/user/views_plugin_argument_validate_user.inc).
Notice: Undefined index: roles in options_form() (line 49 of /home/user/public_html/sites/all/modules/contrib/views/modules/user/views_plugin_argument_validate_user.inc).
At first, I thought it was a views issue, but when digging into views, I noticed something in the array that pointed directly to Ubercart...
Using Devel, If I expand down through the following:
(Array 13 elements)
- 12: views_plugin_argument_validate_user->options_form()
- args
- 1
- input
- options
- validate
- options
- user_or_permission
- perm = view all orders
The problem is, I see this on every single context filter I create on ANY new or existing view and the only module (I have installed) that could possibly utilize view all orders is Ubercart.
I went into the uc_orders view and tried changing the permissions but to no avail... I tried to clear the registry but that didn't help either. Any ideas on how to possibly clear this up? At this point I have no idea if it's site specific or a bug...
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1914874-validate_user_perm-fix.patch | 1.04 KB | longwave |
Comments
Comment #1
DanZ commentedI note that you've marked this issue as Version 7.x-3.2. You should be upgrading from the latest version of Ubercart 2 (6.x-2.11) to the latest version of Ubercart 3 (7.x-3.3 or 7.x-3.x-dev).
What happens if you do that?
Exactly which versions did you use in the upgrade you did?
Comment #2
sah62 commentedFor what it's worth I'm experiencing this same issue with 7.x-3.3.
Comment #3
longwavePlease test the attached patch.
Comment #4
sah62 commentedThe patch in #3 fixed the problem for me - thanks!
Comment #5
longwaveCommitted.
Comment #6
philsward commentedWoohoo! Fixed my issue as well : )
@DanZ: I'm still on 3.2 because I had a few issues with 3.3 (most are already documented & committed). In trying to figure out some other issues I originally thought was caused by UC, I downgraded to see if that would fix them, (it was something else) and I decided to stay on 3.2 since it's not a security release and I didn't like working through some of the stuff that broke between 3.2 & 3.3. Since the site is a pretty big bread winner, I really hate to rock the boat too much with a dev if you know what I mean...
@longwave: That was super fast! Thanks!!