|
Manuel
|
August 29, 2023 at 1:19 pm
Lately we use the add-on Attendee Mover to move people from one type of ticket to another.
For example. A person books ticket A, but made a mistake and should have been ticket B. We use the Attendee mover to change the ticket from A to B. Ticket A is automatically cancelled and a new ticket B is created. Everything seems ok.
However, this old ticket keeps visible for clients in all the communication e-mails. This brings a lot of confusion. We should be able to permantly delete it.
The biggest problem that we have is that after adding the payment to the transaction, the cancelled ticket is also automatically accpeted again and the client have again 2 active tickets. This is obviously not correct. Obviously we could change the setting to not change the status after adding a payment, but this should be straightforward for adding a payment. It’s not normal that we first need to check if there is a cancelled ticket withing the transaction.
Thank you for your help.
|
|
Tony
|
August 29, 2023 at 4:51 pm
Hi there,
However, this old ticket keeps visible for clients in all the communication e-mails. This brings a lot of confusion. We should be able to permantly delete it.
Which emails are you referring to here?
If I recall correctly, they cancelled tickets were original included within the messages so that it could be shown to the user that they had indeed cancelled a previous ticket.
However, I’d like to double-check this so I need to know which emails are causing the confusion.
The biggest problem that we have is that after adding the payment to the transaction, the cancelled ticket is also automatically accpeted again and the client have again 2 active tickets. This is obviously not correct. Obviously we could change the setting to not change the status after adding a payment, but this should be straightforward for adding a payment. It’s not normal that we first need to check if there is a cancelled ticket withing the transaction.
I checked into this and you are correct, payments are applying to ALL registrations by default, including cancelled regs. I’ve created a ticket to change that as payments should not be applying to those cancelled regs by default.
One option you have in the meantime (other than not changing the status on payment) is to click on the ‘Just the following registrations’ radio button. That defaults to all registrations excluding cancelled. The ‘All registrations’ option is literally pulling all registrations.
The next version of Event Espresso will exclude cancelled registrations by default when applying to all, but for now that should get you by easier.
|
|
Manuel
|
August 30, 2023 at 3:16 am
Thank you for this update. Good to see that this will be resolved.
I have just double checked and it’s in all e-mail communication. For example: Payment received, but also payment reminder, multi status …
|
|
Tony
|
September 5, 2023 at 3:18 am
Just a quick update on this.
The latest version of Event Espresso (5.0.10.p) should no longer apply payments to cancelled registrations which should fix the issue you were having with the attendee mover.
Including the cancelled registration within messages was an original design choice and I have created a ticket to discuss this further, the emails will currently still contain those tickets as it stands.
|
|
Manuel
|
September 13, 2023 at 9:47 am
Hello Tony, thank you for this update. I have just tested this, and indeed this bug seems to be fixed. Thank you for that.
However I see now another problem with the attendee mover. I don’t know if it’s related to this new version, or this problem already existed before. But when we move an attendee from one type of ticket to another, I see that the status of the registration also changes to “waiting for payment”. This is certainly not something we want by design. If a status of the registration is for example “not confirmed”. We don’t want it to change this.
|
|
Rio
|
September 13, 2023 at 8:29 pm
Can you tell me the status of it before it was transferred? was it a paid ticket ticket?
Was there any amount difference when it was transferred to another event?
thanks
|
|
Manuel
|
September 14, 2023 at 6:23 am
It was a ticket with status “not confirmed” and no payment has been added to this ticket. After I change the ticket with the attendee mover, the status is automatically changed to “waithing for payment”. Obviously this is not the way to go.
|
|
Rio
|
September 14, 2023 at 11:32 pm
Did try to recreate the issue but was not able to do it. Kindly shoot a video for us? You can use loom to do it.
https://www.loom.com/
thanks
|
|
Manuel
|
September 15, 2023 at 1:41 am
This reply has been marked as private.
|
|
Rio
|
September 15, 2023 at 2:22 am
This reply has been marked as private.
|
|
Manuel
|
September 15, 2023 at 2:37 am
Thanks for your reply. Sorry, but I use Event Espresso in another language, and I didn’t knew what the status name was in English. Since I only see the dutch translation.
It’s certainly not prefarable to change the status of this. For example sometimes a client calls us that he’s on a waiting list or status not approved. But he wants to change to another event/date. So in that use case we certainly don’t want to change his status.
|
|
Rio
|
September 15, 2023 at 4:40 am
You have the option to Trigger the send or not to send the notifications when using the attendee mover. Then if you really want it as not approved, you can set it afterward.
thanks.
|
|
Manuel
|
September 16, 2023 at 10:28 am
Off course I can change the status afterwards, but these are 3 extra clicks/changes that I need to do.
I need to say that no messages need to be sent
Change the status again to not approved
sent a copy of the message
Obviously this is not so user friendly. I think it would be more logic that the status is not changed.
|
|
Rio
|
September 17, 2023 at 5:28 pm
You can select this to “no”, when you’re transferring Not approved.
https://monosnap.com/file/6OGsSBAGswMkcmFeIfoXE1h83S9MF7
But no worries, I did bring this concern to our team and it is under discussion and consideration.
thanks
|
|
Tony
|
September 18, 2023 at 6:55 am
Obviously this is not so user friendly. I think it would be more logic that the status is not changed.
Sure, for your use case, but then not for others so it’s all a balance.
We have to ‘default’ to something and the logic isn’t as simple as just copying the previous registration status as you could be ‘Pending Payment’ but moved to a ticket with 0 value, or lesser value to your current payment and then what happens?
We set it to simply stay the same status and someone else posts that isn’t acceptable, again, all about balance.
—
We’ve opened a discussion with the team to see what options we have here as we need to take in various different use cases for this to work on.
|
|
Manuel
|
September 25, 2023 at 9:35 am
Thank you for the update on that.
|
