Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 3.4.7
    • Fix Version/s: 4.2.0
    • Component/s: CiviEvent
    • Labels:
      None
    • Is MIH?:
      No
    • Code Sprint:
      No

      Description

      Second of Three Jira Issues to stop the Email address being a required field during event registration if a profile has been assigned for the sign up process.

      At present CiviCRM forces in the email address to the events booking process. If the email address is also included in the profile added to the booking process then the email address is removed out of the profile form.

      CiviCRM should be amended so that instead of adding the single email address field into the form it adds the system profile created in http://issues.civicrm.org/jira/browse/CRM-9582.

      Code changes will be to the following routines within the CiviCRM module
      • CRM\Event\Form\Registration\Register.php
      • CRM\Event\Form\Registration\AdditionalParticipant.php
      • CRM\Event\Form\Registration\Confirm.php
      • CRM\Event\BAO\Event.php
      • CRM\Event\BAO\Participant.php

      Test Cases

      • Confirmation email sent to the correct email address
      • Profile email address is carried through all pages, from booking form through to thank you and confirmation email content
      • Contact email address set as entered and is set to primary if new contact
      * Reserved email profile is also injected in Additional Participant forms if "register multiple participants" is enabled
      • De-Duplication is used when the email address is entered (uses default Individual Strict dedupe rule)
      * If default individual strict rule is modified to dedupe based on first + last names or other rules, that deduping works as configured (want to make sure that organizations who configure events to not collect email address have a working contact matching option if desired - else each registration will ALWAYS create a new contact record)

        Activity

        Parvez Saleh created issue -
        David Greenberg made changes -
        Field Original Value New Value
        Parent CRM-9587 [ 23656 ]
        Issue Type Improvement [ 4 ] Sub-task [ 6 ]
        User friendly summary Email Address Optional during Event Registration
        David Greenberg made changes -
        Description Second of Three Jira Issues to stop the Email address being a required field during event registration if a profile has been assigned for the sign up process.

        At present CiviCRM forces in the email address to the events booking process. If the email address is also included in the profile added to the booking process then the email address is removed out of the profile form.

        CiviCRM should be amended so that instead of adding the single email address field into the form it adds the system profile created in http://issues.civicrm.org/jira/browse/CRM-9582.

        Code changes will be to the following routines within the CiviCRM module
        • CRM\Event\Form\Registration\Register.php
        • CRM\Event\Form\Registration\AdditionalParticipant.php
        • CRM\Event\Form\Registration\Confirm.php
        • CRM\Event\BAO\Event.php
        • CRM\Event\BAO\Participant.php

        Test Cases

        • Confirmation email sent to the correct email address
        • Profile email address is carried through all pages, from booking form through to thank you and confirmation email content
        • Contact email address set as entered and is set to primary if new contact
        • De-Duplication is used when the email address is entered
        Second of Three Jira Issues to stop the Email address being a required field during event registration if a profile has been assigned for the sign up process.

        At present CiviCRM forces in the email address to the events booking process. If the email address is also included in the profile added to the booking process then the email address is removed out of the profile form.

        CiviCRM should be amended so that instead of adding the single email address field into the form it adds the system profile created in http://issues.civicrm.org/jira/browse/CRM-9582.

        Code changes will be to the following routines within the CiviCRM module
        • CRM\Event\Form\Registration\Register.php
        • CRM\Event\Form\Registration\AdditionalParticipant.php
        • CRM\Event\Form\Registration\Confirm.php
        • CRM\Event\BAO\Event.php
        • CRM\Event\BAO\Participant.php

        Test Cases

        • Confirmation email sent to the correct email address
        • Profile email address is carried through all pages, from booking form through to thank you and confirmation email content
        • Contact email address set as entered and is set to primary if new contact
        * Reserved email profile is also injected in Additional Participant forms if "register multiple participants" is enabled
        • De-Duplication is used when the email address is entered (uses default Individual Strict dedupe rule)
        * If default individual strict rule is modified to dedupe based on first + last names or other rules, that deduping works as configured (want to make sure that organizations who configure events to not collect email address have a working contact matching option if desired - else each registration will ALWAYS create a new contact record)
        Hide
        xavier dutoit added a comment -
        As you have already a php code, you might want to use the api to create the profile + fields instead of SQL (suggestion, same result obviously)

        As for the dedupe rule, I think it should be selectable (as done recently for the import) to cover all the cases, as you have identified otherwise it will be chaos

        Show
        xavier dutoit added a comment - As you have already a php code, you might want to use the api to create the profile + fields instead of SQL (suggestion, same result obviously) As for the dedupe rule, I think it should be selectable (as done recently for the import) to cover all the cases, as you have identified otherwise it will be chaos
        Donald A. Lobo made changes -
        Fix Version/s 4.2 [ 10680 ]
        Donald A. Lobo made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed/Completed [ 1 ]

          People

          • Assignee:
            Donald A. Lobo
            Reporter:
            Parvez Saleh
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development