Using the development module with fieldgroups, through trial and error I found out that you must have a fieldgroup on each form. Why is fieldgroup required on each and every CCK form?
Also after wading through many errors (cck/content_admin.inc on line 410), I finally found out that each fieldgroup must have a unique name. For example, you can't have a fieldgroup titled "General Info" for a CCK form "Athlete Profile" and "Vendor Info".
Since the fieldgroup is stored using the database relation of CCK type - fieldgroup (i.e. content_athlete_profile - group-general_info) why is it necessary for each fieldgroup to have a unique name?
Possible bug?
Comments
Comment #1
yched commentedFieldgroup names do not have to be unique, but there was a bug in the code that generates a new name when the name already exists.
I committed a fix for this to both branches.
But you need to be more specific about the other issue : "you must have a fieldgroup on each form".
What happens if you don't ? What errors do you get ?
Comment #2
MsDetta commentedIt may be that it was caused by the other error - but when I added fieldgroups to the forms, the number of line 410 errors were reduced.
I'm still receiving line 410 errors, but now it's only 1 per form and only appears on the manage fields page. I'm going to update to your fixed version and see if it clears my line 410 errors.
Comment #3
MsDetta commentedI downloaded the new dev version dated Jan. 9th, turned off the feildgroup module, installed the new cck, turned on the fieldgroup module, updated php. The only difference is that line 410 has changed to line 411.
I've gone through all of my content types and can't determine exactly where the problem lies. On some manage field pages, the error occurs once. On other pages, it occurs multiple times.
I did duplicate a few of the content types. Would this have anything to do with the errors?
Comment #4
karens commentedWhat are all the field modules you are using? This could be coming from a field module rather than from CCK.
Comment #5
MsDetta commentedFor the affiliate profile (no errors), I have:
text,
US zipcode,
US phone,
email
1 Grouping titled affiliate_info
For association profile (has 1 error), I have these fields:
text,
US zipcode,
US phone,
email
1 Grouping titled assn_info
For athlete profile (has 1 error), I have these fields:
text,
US zipcode,
US phone,
email,
date,
image
1 Grouping titled personal_bio
For athlete profile2 (has 1 error), I have these fields:
text,
US zipcode,
US phone,
email,
date,
image
1 Grouping titled personal_info
For athlete school (no errors), I have these fields:
text,
US zipcode,
US phone
1 Grouping titled athlete_school
For athlete school2 (no errors), I have these fields:
text,
US zipcode,
US phone
1 Grouping titled school_information
For athlete stats (4 errors), I have these fields:
text,
integer
3 Groupings titled general_stats, pitching_info, and team_stats
For athlete stats1 (no errors), I have these fields:
text,
integer
3 Groupings titled stats_yr1, pitching_yr_1, and team_yr_1
For athlete stats2 (4 errors), I have these fields:
text,
integer
3 Groupings titled stats_yr2, pitching_yr1, and team_yr2
For bca3 profile (has 1 error), I have these fields:
text,
US zipcode,
US phone,
email
1 Grouping titled bca3_info
For college profile (has 1 error), I have these fields:
text,
US zipcode,
US phone,
email,
link,
image
1 Grouping titled college_information
For prospect profile (has 1 error), I have this field:
text
1 Grouping titled location
For vendor profile (has 1 error), I have these fields:
text,
US zipcode,
US phone,
email
1 Grouping titled vendor_info
It almost appears that the problems are due to the use of "duplicate" except there aren't any errors for athlete school and athlete school2.
PS: Each grouping has unique name due to previous grouping name error (now fixed?). Also, for use with pageroute, I needed to use unique pages so I had to duplicate some cck forms (i.e., stats) because I needed some to have 1 year of info, and others 2 years of info.
Let me know if you want to see site, and I'll open it up for drupal user.
Comment #6
fagoI can reproduce this problem - attached is a simple patch for 4.7 which fixes it, however it should occur in the 5.x branch too, so please review.
the problem is that $disable may be null (not initialized)
Comment #7
yched commentedActually this is most probably a duplicate : http://drupal.org/node/104229
I just committed a fix in the other thread (basically, it's the same as yours :-) )
Could you check that this fixes it for you ?
Comment #8
MsDetta commentedI applied yched's fix (#9 from http://drupal.org/node/104229) and all the errors are fixed. Thanks for your assistance!