Closed (cannot reproduce)
Project:
Field Group
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
16 Dec 2012 at 22:06 UTC
Updated:
28 Sep 2014 at 07:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
xurizaemonComment #2
xurizaemonThink this issue might come up when displaying node field settings for nodes which don't use field_group?
Seen also @ admin/commerce/products/types/CONTENTTYPE/fields - where that content type doesn't use field groups at all.
Comment #3
xurizaemon3 ...
Comment #4
xurizaemonLooks like I need to sort this for field_group/field_group.features.inc in_array() in line 23 also.
Comment #5
xurizaemonComment #6
xurizaemonComment #7
xurizaemonIGNORE
Comment #8
xurizaemonAt some point I may get bored of incrementing this patch in tiny steps and take time instead to read the Field Group codebase, but for now I'm just gonna keep bumping this along :P
Latest patch should include all previous, just to be clear.
Comment #9
xurizaemonComment #10
meichr commentedHi,
I tried to reproduce the error you reported, but was unable to reproduce it by the information you have given. Could you please describe in more detail how to reproduce these errors?
I have tested with
Drupal 7.22
PHP 5.3.14
PHP 5.2.17
Enabled error display by adding
at the beginning of index.php in the root directory.
I also debugged using Netbeans 7.2.1 trying none, one and more empty groups during content type editing under the tab "manage fields" and "manage display" and by node creation and node editing.
When no field is within a field group the variable $group->children within the foreach statement on line 1654 contains "array(0)" and stepping over it produces no E_NOTICE error.
If you could describe the steps and used versions of Drupal and PHP and other conditions to reproduce the errors, I'll try again to check errors and review patches.
Thanks,
Christian.
Comment #11
xurizaemonI think it went like this -
1. Enable field group.
2. Configure field groups on content type TYPE_A.
3. Visit admin/structure/types/manage/TYPE_B/display.
Comment #12
meichr commentedHi,
sorry, still no success in reproducing. This is how I prepare:
Installation
1. Drush makefile in Document root directory: d7fieldgroup.make
2. Drush and Linux commands
Steps To Reproduce
3. Enter URL path admin/structure/types/manage/article/fields
4. Add new group "Article Group", "group_article_group", "Fieldset"
5. Drag field "Body" into group.
6. Save
7. Enter URL path admin/structure/types/manage/page/display
8. No error (E_NOTICE) displayed.
What about the ctools version?
Can you change any of my steps for reproducing?
I also tried adding groups at admin/structure/types/manage/article/display and other combinations.
Thanks,
Christian.
Comment #13
meichr commentedHi,
maybe my drush make script and description were not helpful to you. Are you using drush? Do you have a test site on your local computer to reproduce the error?
At the moment it looks to me that either the error cannot be reproduced or you are using contributed or custom modules which cause your problem and are not mentioned in the Issue Summary. Do you still have this error on your website, if you don't have your patch applied?
Can you describe a minimum setup of Drupal core and contributed modules incl. versions to reproduce the problem?
Comment #14
xurizaemon@meichr - I probably won't have an opportunity to reproduce this, and I agree it's likely due to some other modules installed.
Here's a list of the enabled modules on that site: https://gist.github.com/5719318e7a2e652202e4
I'll mark this postponed, and maybe if someone else runs into the same issue in future, the patch above will help them.
AFAIK it should be harmless, from memory all it does is check that the values referred to in the module code are actually set.
Comment #15
rclemings commentedDISREGARD: There was a problem (two extra, empty field groups) with a profile2 export/import; fixed that and the error vanished. Sorry for the noise.
I think it may be addressfield that's responsible here. At least those are the fields that are giving me this error and I see it's also one of the modules listed in #14.
Comment #16
nils.destoop commented