Skip to content

CRM-19545 Custom field groups missing from views#405

Open
urlisse wants to merge 1 commit intocivicrm:7.x-masterfrom
urlisse:urlisse-patch-1
Open

CRM-19545 Custom field groups missing from views#405
urlisse wants to merge 1 commit intocivicrm:7.x-masterfrom
urlisse:urlisse-patch-1

Conversation

@urlisse
Copy link

@urlisse urlisse commented Oct 19, 2016

Fix for CRM-19545 : "Custom field groups which do not directly extend the base 'Contact' disappear from Drupal view after applying patch CRM-18776"


Fix for CRM-19545 : "Custom field groups which do not directly extend the base 'Contact' disappear from Drupal view after applying patch CRM-18776"
while ($dao->fetch()) {
// call getTree using $dao->id as groupID, $dao->extends as entityType, with possible subtypes in $dao->extends_entity_column_value
$extendsContactSubtype = (('Contact' === $dao->extends) && !empty($dao->extends_entity_column_value));
$extendsContactSubtype = (in_array($dao->extends, array('Contact', 'Individual', 'Organization', 'Household')) && !empty($dao->extends_entity_column_value));
Copy link
Member

@monishdeb monishdeb Nov 4, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can use CRM_Contact_BAO_ContactType::basicTypePairs() instead, which will consider user-defined contact types and sub-types too.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The patch, and this proposed alteration does not fix the issue for custom fields assigned to Relationships. I'll take a look at an alternative solution.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated the issue in JIRA with some additional comments.

@stesi561
Copy link

I think this can be closed. It's very old. Last reference to it on "The follow-up patch @adixon refers to is #405 , which also will not fix the problem (for the reasons mentioned on that PR)."

and 417 got merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants