Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-1786

Billing Location Incorrectly Set as Primary for New Event Registration / New Contact


    • Type: Bug
    • Status: Done/Fixed
    • Priority: Minor
    • Resolution: Fixed/Completed
    • Affects Version/s: None
    • Fix Version/s: 1.7
    • Component/s: CiviContribute, CiviEvent
    • Labels:


      Registering for an online Event as an anonymous user... if the event reg form includes a profile with Name and Address fields (location_type = Home) - the following happens:

      • Billing location created with required Email Address - and this location is set as PRIMARY for the contact
      • Home location created with the Home address info

      Because "Home" is the default location type - the Billing location should NOT be made Primary location for the new contact.

      You can recreate this by accessing this URL w/o logging in:

      (the site is currently configured for PPal Std - not sure if that matters for this bug)

      — Issue Update 4/5 rev 9177 ----

      While you're looking at this... I just hit a related issue while test-driving Event Reg (event id=2) as anonymous user. I submitted "Confirm.php" - but I hadn't logged into PayPal Dev Central so got that error. I hit Back button and logged into PP Dev in a separate tab. Then tried to submit Confimr.php again. I got a fatal DB error on duplicate location type for the contact.

      INSERT INTO civicrm_location (entity_table , entity_id , location_type_id , is_primary ) VALUES ('civicrm_contact' , 134 , 1 , 0 ) [nativecode=1062 ** Duplicate entry 'civicrm_contact-134-1' for key 2]

      I then started over (reset=1) and filled in the same info - hoping that this time it would match on the existing contact and update (not insert) the location records. However, I got the same error. So – it seems like any returning anonymous user who puts in same email/first/last would get this error.




            • Assignee:
              pankaj Pankaj Sharma
              dgg David Greenberg
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: