CiviCRM Community Forums (archive)

Hello,

  I set up a civiEvent.  Instead of using 'attendee' as the default participant role, I created a special one named 'webcast registrant' and assigned that as the default participant role for the event.  I did a search on people that registered for the event, and they were all marked as 'attendee'.  Does anyone know of a patch for this problem.

  I found that because of this problem, logged in users are able to register for the same event multiple times.  The logic in the checkRegistration function of CRM_Event_Form_Registration_Register attempts to find all participants that are tied to the default role for the event.  In this case, the default role is 'webcast registrant', but because everyone is marked as 'attendee', they are not found to be a current participant and are allowed to register again.

  Additionally, and related, I am still running into the issue of multiple anonymous users not being able to register for an event from the same browser.  After an anonymous user registers for an event, the form data does not appear to be cleared out and I think the checkRegistration function is grabbing the already populated e-mail address and preventing the user from re-registering. 

  NOTE:  I commented out the part of the checkRegistration function that was looking at the participant role in order to prevent multiple registrations by the same person.  This is when I discovered that the anonymous registration problem still exists.

  I am using civicrm 2.0.2 and I've incorporated changes to the ThankYou.php and the Register.php files but then I just kind of got tired.  Before I go any further, I was wondering if anyone has:

    1) Seen the problem of participant role not being applied correctly.
    2) Seen the problem of multiple anonymous users not being able to register for an event from the same browser.

  If anyone knows how to patch 2.0.2 to fix these problems, please let me know.  I need to launch webcast registration very soon and am a little stressed about these issues.  Oddly, my current workaround is to leave these bugs in play and just allow duplicate registrations.

  Thanks in advance!
Timothy