[joffrey]

Hi Andras

We tried every solution and we reverted back to providing our customers a code versus us doing back end switching and moving as it involed too many steps and still din’t get the job done.

Any idea if moving/refunding/switching might be in the works, eventhough not a typical scenario? its very common for us, may not be for others!

But thank you for your help!

[joffrey]

The code provided helped us point to the right direction, we managed to generate the data using our own custom id that I’ve mentioned in another post as well.

Thanks for the help Andras!

[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!

[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?

[joffrey]

This reply is private.

[joffrey]

Hi Andras,

Moving the ticket helped! I did a combination of

1. Moving the attendee to the new event/ticket

2. Adjusted the order details on WooCommerce to switch around the ticket and when I re-send tickets through Order Actions, it sent the new data which is great.

3.However the only thing I noticed was that the Ticket ID retained from the old ticket. Is this correct? I can change in phpmyadmin under post meta but it will be tough to teach my employees to go into to do that change every single time there’s a switch.

For item #3 I don’t think it’ll be a big issue since I am replacing it as I’ve mentioned previously but if there’s a solution right now please let me know 🙂

[joffrey]

Hi Andras,

I will give the Moving Tickets option a try!

I actually dont mind that it doesn’t show up on attendees list as long as when I run an export order it will grab all my attendees that have purchased that ticket.

I am working with a developer to adda custom field that replaces the Ticket ID since my other thread wont allow me to create individual unique numbers, so maybe I can ask him to include this “switch/refund” into the workflow as well.

But in the mean time, I wil give me Moving Tickets option a try. I am hoping it sends out an email after the switch or I’m assuming if we resend it will grab new data?

[joffrey]

In regards to the same area, how can we resend / regenerate the tickets once we switch the ticket product via WooCommerce back end? When I click Order Actions to resend tickets after adjusting the order, it sends the OLD info in the email.

[joffrey]

I found the issue, I had missed testing 1 plugin:
Ultimate Addons for Visual Composer

I had to update to the latest version Ultimate Addons for Visual Composer 3.16.18 in order for the tickets to show up under Order Details page in WooCommerce back end.

[joffrey]

This reply is private.

[joffrey]

Thank you!

[joffrey]

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

[joffrey]

Sorry I meant to say I placed this on my functions.php file

/* Tribe, retrive Woo tickets ids for a give post_id - returns array or false if event tickets plus is not active */
function jbs_get_woo_tickets_ids ( $post_id ) {
 
    // bail if event tickets plus is not active
    if ( !class_exists('Tribe__Tickets_Plus__Commerce__WooCommerce__Main') ) return false;
 
    $tickets_provider = Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance();
 
    return $tickets_provider->get_tickets_ids ( $post_id );
 
}

[joffrey]

This reply is private.

[joffrey]

This reply is private.

[Author]

Posts