CiviCRM Community Forums (archive)

I first saw this behaviour on my (prod) Civicrm which is 4.5 beta7 but have just been able to reproduce a simpler version of the problem on the Sandbox site which is 4.5 beta 2.  I don't believe this problem existed in older versions.

In summary, if a person registers more than one participant for the waitlist for a paid event, the total number of tickets and the total amount is not shown properly during the registration confirmation process, in the confirmation email, and in the backend status.  (It is the email which is the most customer-impacting part of this problem).

Steps to recreate the problem in the sandbox:

1. Create an online paid event, set the maximum participants to zero and enable the waitlist.
(It might be deleted by the time you read this, but I used "waitlist test 2" here: http://sandbox.joomla.civicrm.org/administrator/?option=com_civicrm&task=civicrm/event/info&reset=1&id=8).
Note I used a simple Fee structure - one item, one price.

2. Do a live event registration for two participants

3. Register the first participant
see 'first-registration' screenshot - note how the participant is NOT prompted for the fee information. This is a problem if the event is defined with a complex price set as it is failing to capture this information for the first participant.

4. Register the second participant
see 'second-registration' screenshot - this time, it does prompt for the fee information

5. Confirmation screen
see 'confirm' screenshot

6. Email is sent out to user
This is where it is particularly confusing to the customer as the total number of 'tickets' and the total price will never include the first participant.  Eg, on my prod system, customer adds 3 names to waitlist with 2 adults @ £10 each and one child @ £5, they will get a confirm for only two tickets and £15.
(Sandbox doesn't support emails so I haven't included, I can provide examples from my system if required)

7. Back end status
Unsurprisingly, the Events dashboard shows the status differently for the two participants
See 'backend-status'