You sure are quick to close topics to further discussion!<\/p>\n
So, I’ll have to respond to https:\/\/theeventscalendar.com\/support\/forums\/topic\/event-tickets-split-first-name-last-name\/#post-1051182 by starting a new thread.<\/p>\n
One of the events for which we have used The Events Calendar and WooTickets is a festival that takes place at many venues around our town, sometimes with multiple events at the same time. We use volunteers to check people in, and the low-tech paper method works best, at least for now. Volunteers at the box office of the theater handle the paper list better than all the technology.<\/p>\n
Woo Commerce still collects billing info as separate names, so the content that I need is present in the system, I’ve just lost the ability to harvest it — and I guess RSVP “tickets” would still be a single name field.<\/p>\n
In an earlier version I would modify the file class-wootickets.php adding this line:<\/p>\n
\t$lname = get_post_meta( $order_id, ‘_billing_last_name’, true );<\/p>\n
and then then in a file called tribe-tickets-attendees.php I added the next line to get the column in the report. <\/p>\n
‘purchaser_lname’ => __( ‘Purchaser last name’, ‘tribe-events-calendar’ ),<\/p>\n
With new Events Calendar and Events Tickets Plus installed, I tried the following, but it didn’t work: — Can you point me to how I can harvest the last name from the order metadata (which WooCommerce has collected)?<\/p>\n
Plugins\/event-tickets-plus\/src\/Tribe\/Commerce\/WooCommerce\/Main.php<\/p>\n
add Line 944
\n$lname = get_post_meta( $order_id, ‘_billing_last_name’, true );<\/p>\n
add Line 989
\n‘purchaser_lname’ => $lname,<\/p>\n","protected":false},"template":"","class_list":["post-1051350","topic","type-topic","status-closed","hentry"],"yoast_head":"\n