Hi, I have the same issue than described here for the 5.x version of your (really great !) module :
How do I pass an argument from the url to the view?
http://drupal.org/node/248514
I believe that's there's no need for extra php code in views2, as I manage to obtain the result I want with argument and filter in the preview or in a 'panels' layout. but I don't know how to make it appears in QT. it's ok to put a static argument, but don't find the way for url argument.
should I setup a special view (block or page w/ the url/%) ?
what kind of args can I put into the QT arg textfield (node/%, %1..) ?
sorry for this post question as no one complains there must be no problem to do that and there's a doc somewhere.. but did'nt find my way until now :-/
Comments
Comment #1
littleneo commentedthe same view works in a panel, with %1 sent to the view by panel (userID argument set in context/argument)
Comment #2
najibx commentedhmm ...
I don't use argument in URL at all. I thought you define argument in Views2, ie taxonomy ID - Allow multiple terms per argument.
If selected, users can enter multiple arguments in the form of 1+2+3 (for OR) or 1,2,3 (for AND).
then in the QT box can enter, 27,33
Then I can add another view that I can enter 27,32
(note 33 and 32 are two different term ID). But not working, although in my views2 preview it works, an works if I use page views enter example.com/my_page_viewname/27,33
Thanks for sharing
Comment #3
najibx commentedI think for your case, based on http://drupal.org/node/323451, you should use argument handling code in views and don't put anything in QT arg textfield. It's a dynamic, whatver, in the URL.
Comment #4
pasqualledynamic argument handling:
#323451-1: arguments in quicktabs
#332895-1: render quicktab programatically
Comment #5
pasqualleThe issue is without response. Closing..
Feel free to reopen the issue if the problem still exists.
The %1 argument format is not supported by the Quick Tabs module..
Comment #6
Flying Drupalist commentedThis could be similar to my other issue here:
http://drupal.org/node/343016
But I'm running into this too. When trying to create a panel layout with QT inside it the arguments aren't being passed correctly, in either Ajax or non-ajax. Let me try it without panels and see how it works.
Comment #7
Flying Drupalist commentedJust reporting that it's not working any better without panels.
Comment #8
pasquallehow do you pass an argument from a panel to quicktab? I have no idea, as QT uses only fixed arguments. I don't understand what you are trying and how..
Comment #9
yrre7 commentedsubscribing
Comment #10
pasqualle%1 argument format now works in QT. Panels module (and panel arguments) still not supported by QT #236925: Panels 3 as tab content
The issue is without response and this should not be a problem in the latest release. Closing..
Feel free to reopen the issue if the problem still exists.
Comment #11
pasqualleComment #12
jaysadie commentedWhen you have two tabs with each tab using a view, then only the first tab passes the UserId correctly when you select "User ID from URL". The second tab does not return any results.
Comment #13
pasquallejaysadie: please attach a screenshot of the quicktab edit page, views edit page with views argument visible, and the url where you try to display the quicktab..
Comment #14
Flying Drupalist commentedMy usecase:
I'm trying to place a view of some flagged nodes on different tabs.
ie, favorites on one tab bookmarks on another. I'm using panels to construct the user page and sticking the quicktab inside it.
Results: views work only if the argument is User:uid.
User:Name does not work, even though it should (it works without quicktabs).
On ajax quicktabs, the ajaxified tabs do not work unless you use the 'pass additional arguments to views' option in QT admin. I put in %1 and it's fine.
The same is true for Node:title vs Node:nid
Is User:Name / Node:Title something that's not support/will never be supported or would this count as a bug?
Thanks.
Comment #15
pasqualle- arguments from panels are not supported in quicktab (I think it could be possible, but please create a new feature request for it)
- everything from the url is supported by %0, %1...
Comment #16
Flying Drupalist commentedOK, so User:name should be supported right.
I have a bookmarks view:
Argument is User:Name with the flag user relationship.
url is something like: user/username
If I put this onto the user profile it shows the user's flags.
If I put this into a QT with ARGUMENTS: %1 it shows the empty text.
To make it work, I need the ARGUMENTS: %1 as well as User:UID as the views argument.
To me it seems obvious that the problem is with User:Name, because User:UID works fine.
Reading back I think I just repeated what I already said yesterday. Is there some other information I can provide to clarify the matter? Maybe someone else can confirm or contradict my results?
Thanks!
Comment #17
Flying Drupalist commentedI tested it some more. Rather than setting the QT as a view, I set the radio to block and selected the block created by the view.
That works in regular/non ajax mode, but turning on ajax gets some strange behavior. All the CSS and JS (presumably) are reloaded, but the loading bar never disappears and the block never appears.
Comment #18
pasqualledon't do that, that does not work.. #345175: what could be inside ajax quicktabs
what is a user profile?
you need to know what your system url is. In the browser address bar you see an aliased url, that is why you can not correctly use it with quicktabs. put
into page.tpl.php and you will know what you can use and how to set the view arguments..
Comment #19
Flying Drupalist commentedThat issue is about css/js? Nothing about arguments. The CSS/JS has been fixed as far as I can tell. Whenever I click an ajax tab a bunch of css/js gets loaded.
The user profile page is user/username. I put the var_dump there as you recommended and it returns:
array(2) { [0]=> string(4) "user" [1]=> string(1) "1" }
I think that means %1 is alright? ("1" being superuser uid)
I've been doing this. Like I said, User:uid works as expected, totally brilliantly. It's when the views argument is user:name that it croaks.
Please clarify whether or not User:name as argument is something that should work, so I can give up if it doesn't.
Comment #20
pasqualleas your var_dump() shows you do not have user name in the system url, you only have user id..
Comment #21
Flying Drupalist commentedYeah but User:Name normally works for views, and in other tab solutions like views display tabs??? Why doesn't it work here?
Comment #22
netw3rker commented