|
ARAGATO
|
October 26, 2018 at 1:46 am
I know we can set the limit of tickets per oder to 1.
http://uploads.aragato-server.net/screenshots/201810260553e19a73.png
However, we wouild like to have the limit of just 1 ordere of that particular ordered to ticket to max of 1 not only for that first order process, but in general. Thus, if the user tries to register for the same ticket again, it throws him an error (does not work).
Is this possible? If not, what are the starting points for a possbile custom development?
|
|
Josh
|
October 26, 2018 at 6:37 am
Hi,
Would the user be logged into the site (in order to verify it’s the same user that’s already registered) or are these anonymous users that are not logged into the site?
|
|
ARAGATO
|
October 26, 2018 at 8:29 am
Hi, yes the user would be logged in.
|
|
Josh
|
October 26, 2018 at 8:48 am
In that case, you could follow the steps outlined here:
https://gist.github.com/joshfeck/51c2ef122616b48cc4846b1f44384859
|
|
ARAGATO
|
October 27, 2018 at 8:24 am
Hi Josh,
good idea, but not feasable if you have a ton of different tickets, since you had to create a right for each ticket.
I thought about a solution that stores the userID + TicketID in the database and during the booking process this will get checked against. If the same combination (already book) already exists, then booking is denied.
I assume, there is no such solution yet. Which hooks would be the perfect place for checking and writing such data?
|
|
Josh
|
October 27, 2018 at 8:43 am
You wouldn’t use a hook to check against the user. Instead what you could do is write to user_meta when they originally register. Then you could use this hook to filter the output of the ticket selector:
FHEE__ticket_selector_chart_template__do_ticket_inside_row
where you callback function would have to check user_meta to see if they’ve bought that ticket yet.
Alternatively, you could make use of this other posted solution:
https://eventespresso.com/topic/unique-emails-upon-registration/
|
|
ARAGATO
|
November 1, 2018 at 8:47 am
Great solution as always. Thanks Josh. Resolved.
|
