Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I am using Tabs 1.2, together with CCK Fieldgroup tabs 6.x-1.0, and have observed that the tabs functionality breaks if I disable navigation buttons in the tabs configuration.
I don't know if my case is related, but... The content of tabs are not shown when browsing with Internet Explorer 6 (Works perfectly with Firefox). Enabling navigation buttons, changes something but the content is still not shown.
Drupal 6.14
Tabs 6.x-1.2
cck fieldgroup_tabs 6.x-1.0 and the latest dev version
Viewfield 6.x-1.x-dev (latest)
The above was all working before the latest tabs release.
With the nagivation buttons enabled, everything appears in the correct tabs and works fine.
Without the nagivation buttons enabled, the tabs appear but all of the content is on what would probably be counted as the 'basics' tab, and clicking on other tabs makes the content flash the first time you click, and move to where the relevant data is on the second click.
Since this is a live site, I've left navigation buttons enabled, but can switch them off temporarily if you want to see the effect. Please email me (ncunningham crca org au) if you'd like to see the broken version.
I have the same problem on a different installation, here are some screenshot of my configuration and of the node view without my patch, I hope there are useful.
Just wanted to mention that i've spent a bit of time trying to make CCK Fieldgroups work (which depends on this module), and this patch fixed it. Thanks!
Comments
Comment #1
nedjoSteps to reproduce issue?
"breaks" how? Javascript errors?
Comment #2
chaloalvarezj CreditAttribution: chaloalvarezj commentedI don't know if my case is related, but... The content of tabs are not shown when browsing with Internet Explorer 6 (Works perfectly with Firefox). Enabling navigation buttons, changes something but the content is still not shown.
Drupal 6.14
Tabs 6.x-1.2
cck fieldgroup_tabs 6.x-1.0 and the latest dev version
Viewfield 6.x-1.x-dev (latest)
The above was all working before the latest tabs release.
Comment #3
Nigel CunninghamSorry for the slow response.
I've created a node type "Congregation" with data that I'm trying to put into tabs. I'm using cck_fieldgroup tabs too.
http://www.crca.org.au/AboutUs/WhoWeAre/Locations/Cobden shows an example.
With the nagivation buttons enabled, everything appears in the correct tabs and works fine.
Without the nagivation buttons enabled, the tabs appear but all of the content is on what would probably be counted as the 'basics' tab, and clicking on other tabs makes the content flash the first time you click, and move to where the relevant data is on the second click.
Since this is a live site, I've left navigation buttons enabled, but can switch them off temporarily if you want to see the effect. Please email me (ncunningham crca org au) if you'd like to see the broken version.
Comment #4
Patrizio CreditAttribution: Patrizio commentedHere is the code that solved the problem in my case, I hope it can be useful for you.
tabs.js, line 23
replace with
if there were not navigation, didn't applied the function tabs() to the tab
Comment #5
Nigel CunninghamComment 4 fixes it for me.
Thanks Patrizio.
Comment #6
nedjoNot able to reproduce this issue. Likely there's another factor needed, maybe specific fields added to the tabs?
Comment #7
Patrizio CreditAttribution: Patrizio commentedI have the same problem on a different installation, here are some screenshot of my configuration and of the node view without my patch, I hope there are useful.
Comment #8
blup CreditAttribution: blup commentedJust wanted to mention that i've spent a bit of time trying to make CCK Fieldgroups work (which depends on this module), and this patch fixed it. Thanks!
Comment #9
Nigel CunninghamNedjo, do you have suggestions as to how we could find out exactly what is causing the issue?
I've just gotten xdebug installed here, and so can test locally. If I know what to look for, that would help a lot.
Comment #10
Nigel Cunningham