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.
since i updated field group from 7.1.1 to 7.1.2. it is no more applicable with the crm core entities. All display format with field group of any type(fieldset/horizontal/vertical) is just ignored
Comment | File | Size | Author |
---|---|---|---|
#3 | field_group.user-interface.2077695-3.patch | 1.33 KB | FreekVR |
#2 | field_group.user-interface.2077695-2.patch | 721 bytes | FreekVR |
Comments
Comment #1
FreekVR CreditAttribution: FreekVR commentedI am having a similar issue, fieldgroups created for display modes in the user account don't display *at all*, not even a container/wrapper is being added.
Comment #2
FreekVR CreditAttribution: FreekVR commentedI've found out that the user account issue is due to the preprocess function always writing to the 'content' key of the vars array. However, the default user-profile.tpl uses the 'user_profile' key instead. Attached patch fixes this.
Another issue we run into is that we can no longer alter anything related to fieldgroups in our template's preprocess functions. I don't have an idea on how to fix it, since the module uses a theme_registry_alter now to simply add it to the end of the preprocess array. Any thoughts?
Comment #3
FreekVR CreditAttribution: FreekVR commentedI forgot to unset the original variables in the previous patch, here's a rerolled version.
Comment #4
nils.destoop CreditAttribution: nils.destoop commentedThx FreekVR, you're patch has been committed.
ChoY, i tried to install the crm core module. But can't seem to get it working. When i add a new contact through ui, i get fatal errors. So i can't check what's wrong with that entity type. Maybe you can check and create a patch?
Comment #5
nils.destoop CreditAttribution: nils.destoop commented@FreekVR. Change your preprocess functions into process functions. They will run after all the preprocess functions.
We need to alter the theme registry, because we need to make sure all possible preprocess fields are added, before we start grouping.
Comment #6
ChoY CreditAttribution: ChoY commentedthe field_group bug with crm_core entity display is resolved by this patch: https://drupal.org/node/2075039
Comment #7
arx-e CreditAttribution: arx-e commentedI updated today and found lots of my CSS rules were no longer working.
The reason: in filed groups classes the underscores (_) have been replaced with hyphens (-).
Maybe this is related?
Comment #8
ParisLiakos CreditAttribution: ParisLiakos commentedsame here..my css classes are gone, so no styles work..also i noticed that when there are no associated classes with the fieldgroup the wrapper div does not seem to appear at all
Comment #9
ParisLiakos CreditAttribution: ParisLiakos commentedrestoring css classes:
Comment #10
jtalloen CreditAttribution: jtalloen commentedSame here. Everything was working fine with previous version 7.x-1.1.
After the upgrade groupings were completely gone when displaying user account fields.
Not using any crm modules at all.
Comment #11
nils.destoop CreditAttribution: nils.destoop commented#10 do you have this problem with latest dev?
For the missing group-group_name css classes. I suggest that people use the solution of #9. The update hook created the class, but with dashes, not with underscores. Using $group->group_name will re-add the underscores.
Comment #14
nils.destoop CreditAttribution: nils.destoop commented