Hi,
Now, I can make only one tab group with this module, could I make more than one? For example: first two fieldgroups make the first tabgroup and two others make the second tabgroup.
If cannot, could someone shows me what I can modify in code or which module can do that?
Thanks
Viet
| Comment | File | Size | Author |
|---|---|---|---|
| #22 | cck_fieldgroup_tabs.zip | 39.6 KB | rconstantine |
| #14 | nestedgroups02.patch | 1010 bytes | batje |
| #13 | nestedgroups.patch | 1008 bytes | batje |
| #6 | cck_fieldgroup_tabs.zip | 33.89 KB | rconstantine |
| #5 | cck_fieldgroup_tabs.zip | 34.86 KB | rconstantine |
Comments
Comment #1
nedjoCan't be done at present I believe.
Comment #2
nguyenquocviet commentedHi nedjo,
I tried to solve my problem in following way and currently It works fine:
- Make a copy of "cck_fieldgroup_tabs" module folder then rename it to "cck_fieldgroup_tabs2"
- Find and Replace all words of "tabs" to "tabs2" in file names and their content for three files of "cck_fieldgroup_tabs.info", "cck_fieldgroup_tabs.install" and "cck_fieldgroup_tabs.module", except the line "dependencies = fieldgroup tabs" in the file of "cck_fieldgroup_tabs.info", because it just describes what modules this module denpends on, not relating to a new style of "tabs2".
- Then, I install and use it as new module like your original module.
I actually don't understand much what the code is doing, my way of problem solving just comes frome my judge. So, althought it seems to work fine now I don't know if there is any hidden error or mistake that may appear in a specific condition in the future.
Could you please take a look at this and give me your advice.
Thanks and regards
Viet
Comment #3
mitchell commentedMarked #340173: is there a way to make an field group inside a field group? as a duplicate.
This feature may also come through: #300084: Nested fieldgroup.
Comment #4
rconstantine commentedOops. I just posted a new issue announcing my patch for D6 version of CCK which you can find at the same issue quoted above: http://drupal.org/node/300084
Sorry about that. Anyway, my patch allows you to specify certain fieldgroups as tabs (via this module), and then nest regular fieldgroups inside - or just nest fieldgroups of any kind. Out of the box, you can go 10 levels deep in your nesting, but to go deeper you would just have to open the module file and change one number.
Please apply the patch and test if you're interested in this.
I think that the combination of this tabs module, my patch, and the multi-group module are a freakin' awesome combination that multiplies the capabilities of CCK.
Comment #5
rconstantine commentedThis also applies to this: http://drupal.org/node/315015 since I have started to change the AHAH stuff.
Find attached a big change for getting this to work with the latest CCK nested fieldgroups patch here: http://drupal.org/node/300084
I'll roll a proper patch later, but for now you can grab complete files.
Note that filefield probably broke and I'll fix it once we verify that 'normal' fields work. From what I understand, filefield will be getting a patch soon anyway.
The patch to CCK drastically cleans this up and the new hook allows for modules similar to this one to adjust the location of fields and not have difficulty with AHAH.
Comment #6
rconstantine commentedAn addition: I had too many tabs and they were running off of the right side of my screen. Attached are the updated files.
Comment #7
rconstantine commentedThe multigroup and nested fieldgroup patches are now up for review. Once they are in CCK, I'll update this module with the patch above and begin looking at the rest of the issue queue.
Comment #8
nguyenquocviet commentedHello,
I am eager for this new function. Could you please tell when it would be available for usage?
Thank you.
Comment #9
rconstantine commentedIf you track the issues in the cck issue queue, you'll see that two of the three patches needed for these features are nearing inclusion into cck. The third will be reviewed once adjusted for the final versions of the first two patches. After that, the above patch here in this queue will be committed to this module.
Comment #10
k3vin commented+1
Comment #11
rconstantine commentedWithout further comments, I'm declaring this working. I have been using this for months now. As a maintainer, I'll include this in an official release once the 3.x branch of CCK has an official release as well.
Comment #12
bomarmonk commentedGreat: the zipped version of this module in #6 works wonderfully. Thank you for the fixes. I hope this gets committed as the official release, as the current project page release is broken.
Comment #13
batje commentedThis very small patch "nests" fieldgroups in tabs.
The current behaviour of fieldgroups that are no tabs is that they are shown on all tabs of a nodetype (in fact they are shown below the tabset). That is a bit strange.
This patch works very simple: If a fieldgroup that is not a "tabpage" follows a "tabpage" in the Display Order, then the fieldgroup is rendered on the tabpage.
If you still want to show fieldgroups not on the tabset, you can only place them before/above the tabset (as in, before the first fieldgroup that is marked as "tabs"). Feel free to find a nifty little trick to have them after the last tab as well.
This would probably be a new issue, if i had not patched it against #6, as that seems to be the last version of cck fieldgroup tabs.
(I ran the module with CCK 6.2, and this patch only applies to the View mode of a node, as the Edit mode did not show any tabs at all.)
Comment #14
batje commentedAnd against the current .dev version
Comment #15
rconstantine commentedWhy are you making another patch when the one on #6 above works fine?
Comment #16
batje commentedAs I noticed too late that #6 if from January, and there was a commit of the dev code a few days back.
the result is the same for both patches, i just provided them for anyone's convenience.
Comment #17
rconstantine commentedso is it just an update of the same patch? if so, thanks.
Comment #18
batje commentedwelcome ;-)
Comment #19
batje commentedany chance this will be commited to a new version?
Comment #20
nedjoIt would be good to see a patch based on the work rconstantine began.
The approach in #13 and #14, while clever, is a workaround more than a solution and not likely to go in.
Comment #21
klonossubscribing...
Comment #22
rconstantine commentedBeen a while since I've been here. I had to start using the jQuery UI module, which messed up my version of this module found above. Attached is a new version which works with:
jQuery UI module v6.x-1.3 w/ jQuery UI library 1.6
tabs module v6.x-1.3
cck_fieldgroup_tabs module v6.x-1.2
I read somewhere that the jQuery UI module v 1.4 uses the library of 1.7 or greater which requires jQuery 1.3 or greater which doesn't come with D6. So I have not checked out whether that will work or not with the above modules.
Anyway, here is a full set of my files for cck_fieldgroup_tabs...
Note, this works against my (really old) version of CCK as also mentioned above. I haven't had a chance to try out the new patched version from the same thread. Someone else has taken up the 'nested fieldgroup' mantle.