|
ttunnacliffe
|
March 19, 2019 at 9:15 pm
We’re using EE4.
Admin has found ticket showing as sold out.
The ticket is locked and not deletable. On attempting delete, we get message
“Ticket automatically locked….”
It shows as
10792 tickets sold, which must be some error.
how can we delete this ticket to allow us to resume ticket sales.
I know a screenshot will help explain, but I don’t see how to submit one.
Course is
https://cbiaorg.com/events/one-day-clinical-workshop-clinical-reasoning-and-the-application-of-the-model-of-bobath-clinical-practice/
|
|
Josh
|
March 20, 2019 at 9:38 am
Hi,
When a ticket has registrations it cannot be deleted. The reason being is because once that ticket is deleted, the registration will no longer be attached to a ticket.
What you could do is start a new ticket, then set the original ticket’s sell until date to yesterday’s date. Then go to Event Espresso > Events > Templates and set Show Expired Tickets? to No and Save.
|
|
ttunnacliffe
|
March 20, 2019 at 9:46 am
We still have the issue of 10k tickets sold, which has to be some sort of error. Tickets sold should be max 30.
How can we back out of the incorrectly logged 10k tickets sold if we cannot delete this faulty ticket?
|
|
ttunnacliffe
|
March 20, 2019 at 9:47 am
If we can verify there were 0 legitimate registrations for this faulty ticket, can we then get it deleted?
|
|
Josh
|
March 20, 2019 at 10:04 am
Yes there was a recursion bug that was fixed in a recent update of Event Espresso, where the recursion bug had the potential to start a loop of status updates for which there were no actual registrations. That’s been fixed.
What you could do is create a datetime for that event that’s in the past (like the datetime ended last week). Then after you’ve created the new ticket to replace the errant ticket, you assign the errant ticket to the expired datetime. Then un-assign the ticket from the June 22nd datetime.
|
|
ttunnacliffe
|
March 20, 2019 at 10:13 am
I tried what you described. It is not working for me. Issue is that the no. of tickets sold still shows as +10k for both event datetimes, after assigning the errant ticket to the past datetime.
Again, I’d show you a screenshot if you were able to accept it.
|
|
Josh
|
March 20, 2019 at 10:28 am
After you assigned the errant ticket to the past datetime, did you un-assign the ticket from the upcoming datetime?
You can upload your screenshot to your site’s media library, then post a link (or url to the image) in a reply here.
|
|
ttunnacliffe
|
March 20, 2019 at 10:55 am
Ok that helped – Unassigned errant ticket from upcoming datetime. Thanks.
Admin will need still to deal with possible legitimate registrations under the errant ticket. If there are any, can you describe how she can easily transfer them to the new ticket?
|
|
Josh
|
March 20, 2019 at 11:06 am
The attendee mover add-on can be used to transfer registrations from one ticket to another ticket.
|
|
ttunnacliffe
|
March 20, 2019 at 11:17 am
I would have thought so, but I see the registrations that have been moved to the errant ticket are shown as Completed, and there is no link for Attendee mover function. See screenshot:
https://cbiaorg.com/wp-content/uploads/2019/03/Screen-Shot-2019-03-20-at-10.19.26-AM.png
|
|
Josh
|
March 20, 2019 at 11:36 am
The 3 registrations in the screenshot have registration status “Cancelled”. You would need to change the status of those to either Pending Payment or Approved before they can be moved. In other words, Cancelled registrations aren’t intended to be allowed to be moved.
|
|
ttunnacliffe
|
March 20, 2019 at 12:19 pm
I think we’re good now. Tx for help.
Trevor
|
