|
fasten-wellness
|
January 15, 2020 at 2:42 am
In the screenshot you can see that we have many tickets left, why the event is closed for registration on the website?
http://prntscr.com/qnxvmj
|
|
Josh
|
January 15, 2020 at 7:42 am
Hi,
I do not see any reason why it can’t be booked. May I ask what’s the URL of the event? We can take a look and investigate further.
|
|
fasten-wellness
|
January 16, 2020 at 2:19 am
I think I found the reason. Tickets from other events could be used for booking this event too. Now everything is mixed up 🙁
http://prntscr.com/qofzzp
|
|
Josh
|
January 16, 2020 at 6:34 am
Do you mean tickets for other datetimes? If so, that’s a simple fix where you uncheck the boxes next to the other datetimes in the advanced settings of the ticket’s editor.
If tickets for other events are being counted for the event, that’s unexpected but could happen if the events were set up by some other means like via a custom script or API call.
|
|
Tony
|
January 16, 2020 at 6:36 am
Tickers are assigned to datetimes and a single ticket can be assigned to multiple datetimes.
So looking at the screenshot it looks like you’ve set the wrong ticket on the datetime, is that correct?
Note that ‘datetimes’ are not ‘events’, they are an instance of an event but:
>Tickets from other events could be used for booking this event too
Isn’t correct.
Tickets have been set on the wrong datetime(s) within an event.
Now everything is mixed up ?
Do you know which registrations should be on which datetime? Meaning the correct datetime they should have been assigned to?
|
