Upgrading Views user arguments between 2.6 - 2.7
sandino - June 28, 2009 - 23:10
| Project: | me aliases |
| Version: | 6.x-2.7 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
2.7 does not work on my site. Immediately uninstalled and installed 2.6 back. Works now.

#1
Can you please provide more information? What exactly does not work? Are there any errors? Do you have any views that use me?
#2
I created a view of custom type nodes (gallery) that uses an argument User: Uid. And it uses 'me' alias. I have an item in navigation menu 'My galleries' item with path 'gallery/me'
It was working fine untill I upgraded to 2.7 version. I get an empty gallery page (argument not found) when I open 'www.mysite.com/gallery/me'
addition
I tried to install 2.7 version again, run update, cleared cache and got the same result. Also, I noticed a message in argument settings display on the view edit page:
warning: Invalid argument supplied for foreach() in /home/public_html/includes/form.inc on line 1200.#3
Hi, if you read the release notes at http://drupal.org/node/502880, then you might already realize what is going on.
The way me handles arguments in views has changed to make it more flexible, however, I have no way to update all of your custom views in an update script, which is why the release notes say that your views will need to be updated manually.
To do this, you will need to select the user: UID argument in your view, then under the validator options select the "Me" validator.
Once saved, this will make your view work again, and the warning message will disappear.
This validator is very similar to the user validator, with the only differences being that it supports the me alias, and has an option to redirect the "me" alias to a path with the current users uid in place of me.
In future, please read the release notes before posting "Does not work" issues.
I'll leave this issue open for a week or so to allow other users to see what is going on.
#4
I did as you said and 'me' does work now.
I'm sorry for misunderstanding :(
and thank you for this helpful module and for having time to answer!
#5
No problem. Glad you got it all sorted.