views argument from the url

Oh subscribe. Probably the most important thing for me right now.

I anticipate this hugely.

Hopefully I did this right...

This small patch should add this much needed and easy to implement feature :)

Please try it. (See http://drupal.org/patch if you need to learn how to apply it)

Thanks

Subscribing, greetings, Martijn

Doh... that's not good.
Here's an update.

Nothing changed in the argument handling code part - only the addition of str_replace for '%' with 'arg'.
Maybe try downloading the module fresh and applying the patch again.
I can confirm argument handling is still working for me.

Ah, I wasn't using ajax.

Ok, the solution would be to set a js variable - rather than hacking it out of a css id.
No mucking about that way - I'll fix this when I get a chance.
Cheers!

Well, turns out the js variable was already being set, so I don't know why it wasn't being used over hacking it out of a css id. Eeeek.

Anyway... please try it out.

PS. There was another bug where extra slashes were getting added to the view variable (due to not being emptied for each tab).

Cheers

1. I figured the tab.qtid was the id of the quicktab. (The order in which they appear). If this is incorrect, my apologies.
I'll have to setup a few more tab pages and test more thoroughly... to ensure this is the right variable.

2. Firebug :) Unfortunately you can't see the globals unless you reference them. (not a problem in this case)

How did it work for you?

seems to be working fine here. thank you thank you and thank you.

I just tested this on a tracker view as a second tab. It picks up the argument correctly and displays tracker for the proper user as tracker/uid would.

Great work!

Best,
Andrey.

Hmm, the method for getting the correct view args from Drupal.settings was not reliable. I have reworked the patch to add the evaluated url args onto the id string of the tab element. It's working for me but I'm aware that different people have different use cases so wanted to throw this up and see if it works for everyone else before committing.

Ah, never thought of that - good catch. Then I guess we're stuck with passing it through Drupal.settings but it may need to just go in Drupal.settings.quicktabs seeing as there's no reliable way to access the correct ajaxView object from Drupal.settings.views.ajaxViews - even checking against the view name and display id isn't reliable because you could have two instances of that exact same view/display with different arguments.

Changing the status...

subscribing

OK, since getting tab details into Drupal.settings.quicktabs (per #394400: Use Drupal.settings.quicktabs) we now have a reliable way of getting the correct view arguments. The fix committed in http://drupal.org/cvs?commit=184224 is a reworking of pingers' approach using this more reliable method for the ajax views. Please try out the next dev release (should be created a few hours from now) and let me know if there are any issues with this.

Ah yes, I had got rid of all the other info we'd been putting in there and thought I'd better leave something as I think the element's id is used in the progress-loading js, but forgot there would only be numbers left ;-) I'll add quicktabs-tab- or something to the start of it

Hmm, I'm not sure how to handle this... need to look into it more.

subscribing

OK, I've committed a change which I think eliminates problems with non-present arguments from the url (http://drupal.org/cvs?commit=185662). However, during testing I did notice a strange bug with views arguments, which I haven't found a fix for but it is extremely edge-casey:
If you have a QT block with the same view in two tabs but with different arguments, if the second tab rather than the first is loaded on page load (e.g. by accessing it directly with ?quicktabs_0=1 or whatever appended to the path) and it has pager links (ajax-enabled of course), then the pager links mistakenly call the view with the arguments for first tab. However, this second view works perfectly fine if it is loaded via ajax, as it would be under normal circumstances. It also works fine if the QT block is set to non-ajax mode.

Otherwise, I think the arguments are working properly. Please test.

I'm experiencing the same problem as #25 with the latest Dev of 6.12 x 2.x

I have three tabs, all views blocks that depend on the arg(2); of the taxonomy url to populate the blocks.. Only the 1st tab works, I can't ajax load the other tabs, if I ditch the ajax mode all three tabs populate fine. From what I gather none of the above patches would solve this right, it's next on the list?

subs
slightly similar as #25

but with ajax quicktab the view is not displayed if the argument is not provided in the url.
Tried with single and multiple arguments also..

For me only the first tab loads, the rest do not, even if I have the argument in the URL!
This is on plain taxonomy pages, overriden with views. I would show a QT block, but only the first tab loads, even if I pass arg(2) to the block.

Thanks Pasqualle. Meanwhile I solved my issue at #34. For the second tab I had to pass an argument, but only %2 worked for a taxonomy term ajax quicktab, arg2 or arg1 did not. Thought I post it here now that I solved it instead of a new one.

In my view I have the default arg set as this:

$node = node_load(arg(1) );
  $title = str_replace(' ', '-', strtolower($node->title) );
  return $title;

With a relationship of node-reference.

Nothing gets returned on ajax tabs. I think it's part of this issue.

What is this status on here?

Is more information needed or testing needed or something?

Thanks everyone.

Subscribing

subscribing

Sorry to bump this, but it says fixed... I just downloaded QT today and if I test my QT block as a normal block, %1 works fine for the arguments in my views. However, including that block in a panel returns no content.

Is that a different issue, or related to this one?

In response to #41:

I'm getting a similar result in Views blocks that make up my QuickTabs block.
I'm using Context to add the Quicktabs block to the page (which is working).
The end result is a set of QuickTabs with no contents!

Im having the same problem, so panels arent supported at all?

Im having the same problem, so panels arent supported at all?

subscribing

also looking for a fix for issue #25

-------
edit:
fixed my issue here :)
#921264: Quicktabs NID to View

a note stating that
"ajax mode may need additional arguments (%N) to pass them from URL to QT to views"
would had been nice :)

NOTE: This problem seems to carry over into the D7 version. Let me know if I should create a new ticket instead.

Same problem here but with 7.x-3.0. I have a view that takes three arguments. QuickTabs needs to supply %1 and %2 arguments from the URL and the third argument is provided on a per tab basis (eg. "%0/%1/lesson-type1" or "%0/%1/lesson-type2").

If I manually specify the views arguments the correct entries for the "Block" version of the view are displayed. If I replace any of those arguments with a %N the view returns no results and I occasionally get the following error in my logs..

Warning: implode(): Invalid arguments passed in form_error() (line 1593 of /srv/www/htdocs/drupal-7.4/includes/form.inc).

Either I am having a brain fart, or I am having issues. Prob the last part. I am trying to pass arguments to views, as follows.

From the Taxonomy term page url - http://example.com/toyota/ae86-corolla

from the quicktab - %0/%1/engine

the view is built so that it will read /toyota/ae86-corolla/engine and output content, as the chassis and section are 2 separate vocabularies. I am not sure why I am not getting the results, or how to check if the argument is being passed correctly. Any help is awesome as I am struggling with this. Thanks.

Hi bmx269,

What you're asking for is a support request. Please create a new issue for your needs. This issue relates to the creation of the argument handling in the previous version. Resetting version...

Thanks.