Hot answers tagged

4

If you need to exclude all of those email options at once for an export or something I would search up those people, put them in a group, and exclude the group from your searches. To search up that group of people I would use search builder (Search>Search Builder in the main CiviCRM menu) with the following settings: Contacts: Email: Primary: Is Empty Also ...


3

That's it @Carl Miller. I went through each plugin individually. The Slider Revolution Plugin was doing it.


2

This is definitely possible. I've done it to have a custom field store a term id, and user selects from a select list of term names... You need to implement hook_civicrm_customFieldOptions(). http://wiki.civicrm.org/confluence/display/CRMDOC/hook_civicrm_customFieldOptions In this provided example below I am using EntityFieldQuery to fetch all terms of ...


2

There are several extensions designed to do exactly this. First is the aptly-named Option Values Importer. It hasn't been updated recently, and it only does the one thing - but it may be simpler to use as a consequence. There's the configitems extension. This one has a bit more setup, but is great if you have to add/remove values on a regular basis. ...


2

crmLoad is triggered on every action. Try: CRM.$(document).on('crmLoad', function(e, data) { console.log(data); })


1

I'm new here so I'm not sure what protocol to follow to explain 1) how to receive notifications from CiviCRM for the events shown in your screenshot of the CiviCRM Admin panel and 2) what you mean when, in terms of code, when you ask if there is a 'neat' way. In both Drupal, and by extension, CiviCRM there is More Than One Way to Do It. Next, it's not ...


1

You can add easily add predefined fields into the autocomplete results by selecting fields under "Autocomplete Contact Search" under "Settings - Search Preferences". Adding the Birth Date will not be as easy. Technically you could add an additional option group value to the option group contact_autocomplete_options, but that will be pretty much ...


1

We finally poked around and noticed standard option groups with integer values did not use zero. We had used value zero to represent "No". We changed "No" to value 3 and updated the existing records. Once all zeroes were gone, the warning disappeared. Later, we noticed that other radio button option groups use Alphanumeric data type even if the values are ...


1

This was a bug in CiviCRM 4.7 which has now been fixed. See https://issues.civicrm.org/jira/browse/CRM-18456


1

OK, I ended up getting into a rabbit hole and spending more time than expected here! There's a short workaround for you, if you're not trying to edit CiviCase-related option groups: Comment out CRM/Core/Page/Basic.php line 294, which reads: $caseCount = CRM_Case_BAO_Case::caseCount(NULL, FALSE); For the in-depth fix, I've opened a new bug on issues....


Only top voted, non community-wiki answers of a minimum length are eligible