We have a customer that purchased two tickets for the same event with a different variation (i.e. Group A and Group B); the item details appears normal; although when the customer entered ticket holder names, they were not reflected onto the tickets.
Basically the wife purchased two (2) tickets of the same event, different groups; she entered her husbands name as one of the ticket holders, then entered her name as the second ticket holder, unfortunately the ticket(s) don’t reflect this information. In viewing the Order details, you can see the ‘List of Event Ticket Holders’ is correct with her name, then his name, although in viewing the tickets, both tickets show the husbands name.
Also, when I select the ‘Event Ticket Numbers for this Order’, despite the ticket number chosen, the information is the same, it doesn’t show one specific ticket select, it shows both tickets that belong to that order.
Now there is a clue that may help, I’ve discovered previous orders where processed when different people/names were entered into the ticket holder information and the Ticket system created tickets with an ending letter XXXX-XXXX-XXXA and XXXX-XXXX-XXXB (A and B) to differentiate the tickets. The only change between the orders is the most recent version (and patch) update of Eventon Tickets.
We do get orders from groups and/or couples and having the names reflected properly is important and presently it seems the system isn’t reflecting the names or creating unique tickets based on the ticket holder information; please advise.
Thanks!Feb 6,2017 AT 5:25PM - 3 years ago -
It seems this may be an issue with variations, I have previous orders that have two (2) people purchasing the same event with the same variation our variations are classified as groups. So an example is that someone purchases two (2) events then selects the variation ‘Group A’ for both event purchases, it appears that unique tickets that properly identify the individual ticket holder names are created, those tickets also show letters at the end of the ticket numbers (i.e. A or B).
In the aforementioned situation, the wife purchase two (2) events, of the same venue/date, however she chose different variations, her variation was ‘Group B’ and the second event was a variation of ‘Group A’. As a result, when the tickets are generated only one ticket holder name was generated and the ticket numbers created were not uniquely identified with A or B endings based on my initial investigation.
This could pose a huge problem for couples and/or groups purchasing events with different variations (i.e. groups).
I’m going to post another follow-up in private that contains links to the order in question, in addition to examples of other orders that worked, but didn’t have different variations selected.
Lastly, I can’t discount that the issue is potentially upgrade related, as the ticket plugin was upgraded/patched recently.
In recreating a similar order as to the one that doesn’t reflect the correct ticket holder name, here was the process:
1. Opened a specific event date/venue.
2. Selected variation (i.e. Group A) -> Added to Cart
3. Selected variation (i.e. Group B) -> Added to Cart
4. Selected ‘View Cart’, both events with different variations were shown on two different product # items.
5. Selected ‘Proceed to Checkout’.
6. During the billing information entry I was asked for Ticket Holder Name #1 (twice), as it seems the ticket software see’s the two different variations as two different tickets and each ticket has a different holder name?
7. Selected ‘Place Order’
8. Viewed ‘Pending Payment’ order within WooCommerce/WP Admin and noted the ‘List of Event Ticket Holders’ was correct with two different names listed.
9. The Event Ticket Numbers for this Order has two different numbers (no A or B), although when selecting either ticket #, two tickets were presented, despite only selecting one number. The same result for the other and the primary ticket holder name wasn’t properly reflected.
That said, it seems the previous A/B identifiers are more-so for ticket orders of the same event and same event variation, thus they ask for Ticket Holder Name #1 and Name #2, etc.. however when purchasing event tickets for the same event with a different variation, the software asks for Ticket Holder #1 twice. As for the ticket numbers, while unique ticket numbers are created, the content isn’t properly reflected, we’ll need Ashan to review the coded behavior.
That’s the current state of my recreation process; during these stages I disabled non-essential plugins, same result was presented.
Hopefully further details in addition to a patch can be made available as we’re on the verge of having dozens of event purchases in this manner within the next few days and the management/tracking and check-in part would be problematic to say the least. The latest purchaser has demanded the primary ticket holder names be corrected, sadly, I have no ability to comply with that request.
Your advice, help and support is needed and welcomed.
Are you sure you dont want to say anything else ? 🙂 for a guy that hate reading this is a lot of writing… let me get my coffee and read this later and get back to you 🙂
To think, this was the abbreviated version! 😀
Ok Mark, I finally had the brain capacity to sit down and read your message and yes i can also recreate this issue. Ticket capture both names but ticket email have only first person’s name. Man this is a tough one… cus if i change the way we save ticket holder names its gonna effect old tickets thats already sold so we have to add separate system as backup.
Alright i will see what I can do here.
We are going to need some more time to fix this issue Mark. Its a really tough one. If you have any suggestions please let me know.
I know that your incredible busy specially with the latest WC v3.0x update, although I was curious if any progress had been made on this ticket issue. As our season starts to take off, we’re seeing a single person purchasing multiple tickets with different variations, specifically our group selection and while EVO Tickets requests ticket holder names, it’s not recorded to the attendees inventory and the tickets are not assigned properly causing a check-in issue at the event.
Just checking. 🙂
We did get several updates out for tickets addon that was compatible with latest WC version. Are you on those latest event ticket version and still having this issue?
So the issue is when someone purchase several variation items the additional ticket holder names not getting assigned correct to those additional tickets right?
We’ve tested the very latest version on our development site (sadly we’re not ready to move to WC3.0 due to other issues with compatibility), that said we did setup a WC3.x development site for testing and yes, we’re still having the same problem mentioned in the initial post.
Basically if someone purchases a different variation, while the ticket(s) are created, the reflection on the ticket holder name isn’t correct.
Lastly, since we can’t edit ticket holder names as a quick fix, otherwise we would simply correct the ticket holder names and resend the tickets.
and thank you for all the hard work! (Now if we could only get an updated EventON Tickets that worked with WC 2.6.x) 😉 🙂
i know we have realized the issue with additional ticket holer names and variations and we are hoping to find a solution for that as well 🙂
Hi there – is this issue supposed to be resolved?
U updated to the latest version?
Christian sorry for the delay please update ticket addon to version 1.7.6 and that will resolve this issue.