The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Installing FG caused the vertical tabs for node tools at the bottom of the node editor (such as Path alias, Publish, Comments, etc.) to disappear. This has actually been since quite some time. Returned to the problem with a fresh FG update (build of 2012 Mar 12) - to no avail.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | no-vtabs.png | 5.83 KB | moniuch |
| #3 | no-vtabs-manage-fields.png | 44.39 KB | moniuch |
| #3 | no-vtabs-edit.png | 20.93 KB | moniuch |
Comments
Comment #1
moniuch commentedsorry, one of the tests proved it was not FG. closing
Comment #2
moniuch commentedSorry, I have to re-open this issue anyway, but perhaps as a support request.
I'm facing a strange situation with one particular content type on my site. As it contains more than 20 fields, I wanted to organize them into related groups and used Field Group module to create vertical tabs for those groups. This works perfectly for all other content types, but this one.
The symptoms are:
when using Vertical Tabs Group and then nested Vertical Tab - the groups show as expandable accordions.
when using Vertical Tab without any wrapper - the groups do not show up at all.
I cannot judge how much of the problem pertains to Field Group and how much to the core integrity of the content type. But I hope you could advise on how to heal the content type, maybe you could tell me what field to check in the database of my site, maybe you have some kind of a rebuild tool that could perform an integrity check?
Comment #3
moniuch commentedAttached please find some screenshots of how it looks in the faulty content type
Comment #4
hydra commentedApparently you forgot to add the vertical tabs group! It will provide the wrapper for vertical tab items. You have to nest the items inside the group. Please use the 7.x-1.x version of field group instead of 7.x-2.x, thanks!
Comment #5
Stalski commentedAs Hydra says, The 2 branch is not better. It only has code that is very tricky and could lead to a messed up site.
So be careful and realize why you want the 2 branch (there are only a couple of real reasons)