[Bruce]

Perhaps a better alternative is to hide the Attendees via CSS – that way any future DB updates won;t switch them back on:

.tribe-attendees-list-container, .tribe-tickets-attendees-list-optout {
display: none;
}

[Bruce]

Hey Chris,

I ran into the same problem, but found a solution. Add the following to your themes functions.php and you can add the phone and address details to the CSV.

I found this hook in https://theeventscalendar.com/support/forums/topic/export-out-attendees-list/

/**
 * Adds extra columns to the attendee export data (CSV only).
 *
 * Filters via the tribe_events_tickets_attendees_csv_items hook; intended for use
 * with the initial 4.1 release of Event Tickets only.
 *
 * @param  array $items
 * @return array
 */
function attendee_export_add_purchaser_email_name( $items ) {
    $count = 0;
    $order_id_col = 0;
    $idx = 0;

    foreach($items[0] as $col_name) {
      if (strtolower($col_name) == "order id") {
        $order_id_col = $idx;
        break;    
      }
      $idx++;
    }

    foreach ( $items as &$attendee_record ) {

        // Add the header columns
        if ( 1 === ++$count ) {
            $attendee_record[] = 'Customer Phone';
            $attendee_record[] = 'Address 1';
            $attendee_record[] = 'Address 2';
            $attendee_record[] = 'City/Town';
            $attendee_record[] = 'State';
            $attendee_record[] = 'Post Code';
        }
        // Populate the new column in each subsequent row
        else {
            // Assumes that the order ID lives in the first column
            $order = wc_get_order( (int) $attendee_record[$order_id_col] );
            $attendee_record[] = $order->billing_phone;
            if (strlen(trim($order->shipping_address_1)) > 0) {
              $attendee_record[] = $order->shipping_address_1;
              $attendee_record[] = $order->shipping_address_2;
              $attendee_record[] = $order->shipping_city;
              $attendee_record[] = $order->shipping_state;
              $attendee_record[] = $order->shipping_postcode;
            } else {
              $attendee_record[] = $order->billing_address_1;
              $attendee_record[] = $order->billing_address_2;
              $attendee_record[] = $order->billing_city;
              $attendee_record[] = $order->billing_state;
              $attendee_record[] = $order->billing_postcode;
            }
        }
    }
 
    return $items;
}
add_filter( 'tribe_events_tickets_attendees_csv_items', 'attendee_export_add_purchaser_email_name' );

[Bruce]

Hi Hunter,

I changed ‘Create recurring events in advance for’ from 1 month to 2 months, and hey-presto all four recurring events for January 2017 were created.

Thanks for your help.

Bruce.

[Bruce]

Hi Hunter,

Thanks for the reply. I’ve followed the steps in the Testing for Conflicts link.

Because it is a live site, I used my staging site to test, but checked before making any changes that the problem was identical on both the staging and live sites.

I did switch to the 2016 theme, then disable all plugins other than TEC and TEC Pro, cleared my browser cache and then re-tested. I used the identical event setup as shown in the screen shot, and it created one only event (5 Jan 2017), even though it should have created one event for each Thursday in Jan 2017.

Bruce.

[Author]

Posts