Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.-First great module, thank you.
I have a QT set of three tabs and the third tab has another QT set of three tabs. for testing purposes I have loaded the same ajaxed view with an exposed filter into each so that I could verify the usability before development.
I noticed that in order to get the second and third tabs on the first level, to correctly use the ajaxed view, I had to have all tabs load when the page loads. Meaning I could not use ajax to load the tabs when they were selected. So now all tabs load when the page loads.
Each of the first level tabs handle the ajaxed view correctly, allowing the view to refresh within the tab. The second level tabs however, do not load the ajaxed view correctly and instead force the page to refresh sending you back to the first tab.
Is there a way to prevent this from happening or should views not be placed within nested tabs?
Trevor
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | qt_js_machine_name_bug.patch | 485 bytes | mrjeeves |
Comments
Comment #1
pasquallethis sound like your view is not an ajax view, please check: edit view->Basic settings->Use AJAX
also I do not understand why you have to load your views at page load, views should work correctly within ajax quicktabs
Comment #2
break9 commentedI am using the same view in all six tabs for consistency and testing purposes. The view is an ajax view.
I am not sure what you mean by "ajax quicktabs" BUT:
if i use ajax (AHAH) to load the tabs as they are selected then the ajax in the view only works properly on the first tab (the default loaded tab) - this was not my question but if it is also an issue than I suppose we should address it.
Anyway, currently all tabs load on page load and only the level one tabs allow the ajax view to function as expected. The view (same view as the others) within the nested tabs does not perform an ajax request but simply sends the page to the default page of the view. (in this case it happens to be the same as the page I am testing)
Trevor
Comment #3
pasqualleI can reproduce the first problem. created a new issue: #449170: view filter in ajax quicktab
Comment #4
pasqualleand the second problem seems like the same as the first, as it works for me with a nested non-ajax quicktab.
change the nested quicktab to non-ajax also
edit quicktab->Ajax: No: All tabs will be loaded at page load.
Comment #5
break9 commentedboth quick tabs including the nested are non-ajax. I can not get a ajax view within a nested tab to perform properly.
Are you saying that when you create a quick tab (non-ajax) and you nest a second quicktab (non-ajax) with an ajax view (and exposed filter) in the nested quicktab, that the ajax view and exposed filter execute as expected within the nested tab?
Mine does not.
Trevor
Comment #6
mrjeeves commentedI have had the same issue, attached patch is rolled against the 6.x-3.x-dev
Comment #7
mrjeeves commentedforgot to tag
Comment #8
netw3rker commentedComment #9
avpadernoI am closing this issue, since it's for a Drupal version no longer supported.