I have a simple QT block with two tabs each pointing to a unique node id. Each node is only a paragraph long, containing some words and an image. The QT block is then placed in its own region on the front page where there is no other AJAX happening.
If I select "No: All tabs will be loaded at page load." the tabs work fine. Very easy in fact to create and view them. Changed the theme, works in each one. I was very happy with that - thanks.
But... ;)
If I select "Yes: Tab content will be loaded at tab click." the first tab loads and works, but the second tab comes up blank. Nothing in the content.
We do use a reverse proxy if that makes a difference with path names?
And were are quite interested in performance so AJAX does make sense for us I think.
Thanks
Comments
Comment #1
pasqualle1. Do you have block caching enabled?
2. Does it works with Garland theme?
3. Does it show the "Loading" progress bar?
4. check your
<head>section in your page source. Can you find these lines? :Comment #2
Plazmus commentedI have exactly the same problem.
1. Cashing disabled
2. It doesn't work with my custom and Garland theme as well.
3. It is blank, there is no "Loading" bar
4. Yes quicktabs.js is in head section
I tested 6.x-2.0-rc3 and 6.x-2.x-dev both are not working.
Comment #3
pasquallemy test:
Any idea what should I try to reproduce the problem?
Comment #4
pasqualleissue #400448: All tabs show first tab content seems very similar, but I can't reproduce neither this nor that..
Comment #5
Plazmus commentedI don't have clean URLs enabled, also I have many modules installed what might be a problem.
I will try do more tests and let you know.
Comment #6
pasqualleComment #7
Plazmus commentedI found were the problem is!
I disabled 'Devel' module and all tabs now display content, so there is some kind of conflict with this module.
Comment #8
pasqualleComment #9
tamanna-freelancer commentedI also had both devel and quick tabs installed.So in views when I was changing the footer the input formats were not displaying.
Hope this helps.
Comment #10
pasqualleThis issue might be fixed with #588398-3: Content-Type for ajax - set header to text/javascript
Comment #11
katbailey commented