|
Sebastien Matte
|
March 26, 2014 at 11:01 am
Hello, I have multi-registration integrated for a serie of 5 concert nights. Users can register two tickets by user, one for them and one for other, for any or all nights. The default payment status is ‘pending’, when I receive a check deposit I can confirm them to ‘completed’. That part works well, but they might be ‘completed’ for one night and not the other, depending on their spot in the waiting list.
But now, if a user register exemple for the first two nights for him and someone else, when I receive their own deposit and I ‘complete’ the payment for them it will automatically ‘complete’ the payment for all the tickets they booked, for them and for the other, and for all nights.
My problem with that behavior is that I use this ‘completed’ process to get them to know if they can actually come for a particular night or must still wait for a spot, so I need ‘ granular’ ‘payment completed’ option, so that when I ‘complete’ for only one night but not the other nor for the other people they booked then I don’t get the whole tickets bunch to get the green status, only that particular, precise night. Is that possible ?
Thanks,
– Sébastien
|
|
Tony
|
March 27, 2014 at 5:20 am
Hi Sebastien,
When using Multi Event Registration, the payment for all the attendees is linked to the Primary Attendee so effectively there is only 1 payment to edit (editing a Secondary attendee payment actually takes you to the Primary attendee payment). Setting this Payment to complete will show as complete for all the attendees as you explained.
Unfortunately with EE3 there is no way to work around this.
If you want the Attendees to be able to pay separately for each night, and use Event Espresso to manage this, they would need to make separate registrations for each night, without using MER.
|
|
Sebastien Matte
|
March 27, 2014 at 6:35 am
ok, I understand how it is currently working. For my users it is really convenient to be able to use multi-registration, and for me it would be perfect to be able to confirm them in their individual tickets, separately of each booking and of each others.
Do you see a way of implementing this ? Would EE4 bring that functionality ?
Or could a support token implement this in not too long a time ? I’d be willing to pay for this as I don’t know how to fluidly organise my functioning without this; it’s doable, by the way you explained, but the user experience then degrades. ‘Un-linking’ their payment status in the function is what I need 🙂
Thanks for any imputs or better solutions,
– Sebastien
|
|
Tony
|
March 31, 2014 at 10:11 am
Do you see a way of implementing this ?
Not with EE3, the system has been designed this way and as such is not something that can easily be altered.
With Priority support we will often make small, minor modifications but this is a rather large customisation which is not something we could take on at this time unfortunately.
Would EE4 bring that functionality ?
EE4 separates Registrations from Transactions, registrations can be approved regardless of the transaction status. When applying payments to a transaction you can chose if this will alter the Registrations attached to that transaction. In your case you would set this to not update the status and then manually Approve which Registration you prefer (which ever ones the payment applies to).
Does that sound like it will work better?
Note EE4 currently does NOT support any of the Add-on’s, including the Calendar. Before installing EE4 onto a live site I recommend installing a copy locally to see if it will suit your needs first. Be sure to create a full site backup before you do update to EE4.
|
|
Sebastien Matte
|
March 31, 2014 at 12:23 pm
ok, thanks — I’ll manage for these inscriptions [ the first batch is starting friday ] then I’ll see where EE 4 is at in september, for the next ones 🙂
– Sébastien
|
