i dont know what's wrong now. quicktabs was working but now it has again a problem:

the third tab is shown under (!) the second tab and not in the third one. the third is empty. first tab shows it fine

my setup:

non-ajax quicktab block with 3 tabs. this quicktab block is inserted into a panel to make it accessible on the main page.

please have a look:

http://www.notfallseelsorge-muenchen.de/weiterfuehrendes

click on the second TAB ("Litaratur") and on the third TAB ("Materialien") and you will see my problem as described. I dont use block cache. i turned on CSS compression and JSS compression. i cleared the cache on the site and in my browser... still i have this problem.
Please help me as this site is already up and running. My clients are getting slowly annoyed :(

THANKS!!!!

CommentFileSizeAuthor
quicktabs.jpg287.35 KBdrupalok

Comments

drupalok’s picture

drupalok commented

i just saw that it does work (!) on the second site this drupal installation runs (it is a multi-domain-site based on the module "domain access")

http://test.katholische-notfallseelsorge-muenchen.de/weiterfuehrendes

this is the same quicktab and it does work there! (i checked it using the other theme but it does not work with it either).

so... what's going wrong? can quicktabs break if there are too many nodes in it? (on the site where it does not work there are more nodes than on the other)

anyone?

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Category: bug » support

Your second tabpage is an invalid HTML (missing </div> ) and it is causing the problem. The HTML structure is wrong, and the browser interpreted it as the third tapage is being inside the second.

use http://validator.w3.org/
or the firefox plugin: Html Validator

drupalok’s picture

drupalok commented
Status: Active » Fixed

thanks a lot! i found the problem.... i was trimming a text area and forgot to click the "field can contain html" button... so div tags get closed!

thanks again! :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.