Ticket_ID per each product of an event

[joffrey]

I have multiple products per event and I had thought each product will generate its own “numbering system”

For instance:

Event 1
– Ticket a – 500 stock
– Ticket b -500 stock

And when one person purchases both Ticket A and B, I had thought it would generate TICKET A-1, TICKET B-1. But instead it is doing Ticket A-1, Ticket B-2.

How can I change this so that each product has its own numbering? I can manually change the post_meta values for the old orders but going forward I need to make sure it creates itws own numbering.

[joffrey]

This reply is private.

[Victor]

Hi Joffrey!

Thanks for getting in touch with us! Let me try to help you with that.

The ticket unique ID works that way by default and there is no built in option to modify it. However, you could modify this behaviour with some custom coding.

We are limited in the amount of support we can give for this type of customizations, but we always like helping out and at least point you in the right direction as much possible.

If you decide to go into customizing this, you should take a look at the ‘event_ticket_woo_attendee_created’ action hook provided to modify the unique id for the attendees generated.

I hope that helps. Let me know if you have follow up questions.

Best,
Victor

[joffrey]

I would appreciate some help or direction on this. Thanks I wil wait

[Victor]

Hi Joffrey!

I will reach out to the team to see if we can come up with a snippet to have as a starting point to achieve that.

I’ll get back to you as soon as we have something. Please hang in there.

Thanks,
Victor

[joffrey]

Filter hook: tribe_events_tickets_attendees_table_attendee_id_column

Are there any implications in overriding $unique_id from that hook with non unique value?

[Victor]

Hi Joffrey!

Thanks for following up with this.

I don’t think there any implications in terms of the integrity of the records using that filter, as it does not affect the database.

Trying to come up with a working snippet using the ‘event_ticket_woo_attendee_created‘ action hook, I did find there might be certain security implications as the assign_unique_id() function triggered does affect the database. So I could not think of a way to accomplish that.

If using the ‘tribe_events_tickets_attendees_table_attendee_id_column’ filter works for you by overriding the $unique_id that is returned, then that’s one way to go. I’m not exactly sure the goal of this change, but bear in mind that will only modify the output in the attendees table.

I hope that helps! Let me know if you have any follow up questions.

Best,
Victor

[joffrey]

Thank you for your help, we managed to override and do a customization. We are using our own unique ticket id and replaced it with the ticket_id generated via tribe for each ticket per event. Which helps trumendously for our setup!

Thanks for your responses and guidance!

[Victor]

Hi Joffrey!

That’s great to hear! I’m glad you could accomplish that.

I’ll go ahead and close this thread, but don’t hesitate to open a new topic if anything comes up and we’ll be happy to help.

Cheers,
Victor

[Author]

Posts