[Ryan]

We’re working on ways to make it more portable between tickets/events/sites but that gives you the general idea 🙂

[Ryan]

Edit the /includes/trigger/WC_Zapier_Trigger_Order.php file. Insert the new code around line 363.

I’ve included some existing code in the snippet below to give context.

                // Customer Notes (Private Notes aren't included)
                // Arrays are not very well supported by Zapier at this point, but we'll send the data anyway
                $order->notes = array(); // Array of order notes
                foreach ( $this->wc_order->get_customer_order_notes() as $order_note_data ) {
                        $note               = new stdClass();
                        $note->note         = $order_note_data->comment_content;
                        $note->date         = WC_Zapier::format_date( $order_note_data->comment_date );
                        $note->author       = $order_note_data->comment_author;
                        $note->author_email = $order_note_data->comment_author_email;
                        $order->notes[]     = $note;
                }

                // event ticket data : Strider
                $order->ticket_info      = array();
                $ticket_meta = get_post_meta( $order_id , '_tribe_tickets_meta') ;
                $ticket_meta = array_pop( $ticket_meta );

                foreach( $ticket_meta as $key => &$meta )
                {
                        foreach( $meta as &$data )
                        {
                                $data['time']           = $data['preferred-time-slot'];
                                $data['children']       = $data['we-require-childcare-for-the-following-number-of-children'];

                                unset( $data['preferred-time-slot'] );
                                unset( $data['we-require-childcare-for-the-following-number-of-children'] );
                        }
                }

                $order->attendee_info = array_pop( $ticket_meta );
                error_log( print_r( $order, true ), 3, dirname( __FILE__ )."/log.txt");
                // --- ticket data end --- //

                // Order data needs to be an array.
                $order = (array) $order;

So far this is working for us. There’s always the possibility of refinement 🙂

[Ryan]

Interesting. It seems to be a further conflict with The Events Calendar.

Cornerstone + Event Tickets + The Events Calendar
– No Cornerstone editing tab
– No option for requesting attendee info

Cornerstone only
– Editor works fine

Cornerstone + The Events Calendar
– Editor works fine
– Obviously no ticket sales or options

Cornerstone + Event Tickets
– Editor works fine
– Able to request attendee info
– No Event Calendar

Note: I have the Event Tickets Plus and The Event Calendar Pro plugins as well, but toggling the Pro/Plus versions does nothing. It’s the base plugins that impact functionality.

[Ryan]

We were able to resolve this by modifying the Zapier plugin. Thanks for the tip on where to look for the attendee info.

[Ryan]

Ok, so the attendee info for Woocommerce orders isn’t actually stored in any Woocommerce meta fields. It’s only in the custom post meta field.

I’ll let you know if we get anywhere.

[Ryan]

Thanks, Geoff.

I’d like to say that it’s set up that way for a good reason … but it’s really more about elderly bureaucracy and lack of understanding. Trying to convince them to change how they handle their finances has been a losing a battle.

[Ryan]

Thanks for your help with this.

System info has been posted as requested.

[Ryan]

This reply is private.

[Ryan]

Indeed, Christian. It looks like they are going backwards, giving us less info in the exports instead of more 😉

Thankfully they have acknowledged the problem and promised to fix it (at an undetermined date of their choosing).

I know bugs happen, but in my limited time using this plugin I’m thinking a little more investment in QA before release will solve a lot of headaches.

In the meantime I can offer you the same thing as Paul: A fix that works with Tickets 4.1.3 and Tickets Plus 4.1.2, completely without any warranty or guarantee, 120% use at your own risk. 🙂 It’s working on two of my sites. Email [email protected] if you want it.

[Ryan]

I can confirm the snippet has no impact and doesn’t correct the export issue. However, we have implemented a fix of our own that does work. It’s based on Event Tickets 4.1.3 and Event Tickets Plus 4.1.2.

Would it help if we shared this with the dev team?

As it stands we can’t update the plugin without losing our fix. It would be great if future updates had a working export as soon as possible.

Paul: If you want to try our fix (unofficial, not supported by TEC, nor by us, no warranties, use at your own risk, etc…) email me at [email protected]. I understand the urgency – we’ve been using this plugin for a baseball league where the season started last week, and for a conference we hosted on May 30th. Sometimes waiting for the official fix is rather perilous.

[Ryan]

Sorry – but this snippet has no impact at all.

[Ryan]

Clair,

Your first screen shot with the missing “View Details” link is exactly the result I got with batches of 5 and 6 attendees. When I investigated there was no data added to the postmeta table for those tickets. This makes me think there must be a logic error in the code that chokes past 4 attendees.

You’re right – it’s a pretty significant problem related to a core feature of paid software. Hopefully the team here can get it sorted quickly.

Hunter, I know you don’t like to give timelines on fixes, but surely behind the scenes there is a prioritization method for bug reports – and something like this should hit the top of that list.

[Ryan]

I just recently report a bug (which has been confirmed) regarding the handling of some special characters.

I first noticed the problem when batches of 6 and 5 tickets on one order were purchased with no attendee info stored. Troubleshooting that lead to the discovery of the special character issue. It’s also possible, though, that the size of the batch was a problem for us.

We stopped troubleshooting the batch size issue and attributed it to the characters issue. Perhaps they were both at play.

[Ryan]

Thanks for this!

[Ryan]

Well, that solved it. Thanks!

Is this bug going to be addressed in the next release?

[Author]

Posts