CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Drupal/4.5 - function canProfilesDedupe
Pages: [1]

Author Topic: Drupal/4.5 - function canProfilesDedupe  (Read 205 times)

rocxa

  • I post occasionally
  • **
  • Posts: 40
  • Karma: 4
  • CiviCRM version: 4.5.5
  • CMS version: Drupal 7.34
  • MySQL version: 5.1.71
  • PHP version: 5.3.3
Drupal/4.5 - function canProfilesDedupe
September 23, 2014, 05:11:51 am
The function:

canProfilesDedupe in CRM/Event/Form/ManageEvent/Registration.php line 729

requires that any fields in the dedupe rule are also *required fields in the selected profiles on the event/contribution form.

Line 791:: $combos[$icombo][$ifield] = ($combos[$icombo][$ifield] != 2 && !$field['is_required']) ? 1 : 2;

Is there a reason why the fields need to be *required rather than just on the form?

I can see why they need to be on the selected profile forms so that the dedupe rule has a chance of being useful, but making the profile fields required means that you have to either; force people to fill out data they may not have (losing donations/registrations) or lose the dedupe facility on those that do actually fill out the fields.

My thoughts are that the required aspect of the canProfilesDedupe chgeck should be removed or optional?


Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Drupal/4.5 - function canProfilesDedupe

This forum was archived on 2017-11-26.