tweak to phone number handling in CSV
This commit is contained in:
@@ -1261,6 +1261,8 @@ function _booking_form_submit_post_triggers($node)
|
||||
{
|
||||
global $event;
|
||||
|
||||
//do these triggers really do anything? The partner id and bf/gf id won't be set in initial submit
|
||||
|
||||
//if booking_partner_id is set, make sure the nid it refers to has this node as its booking_partner_id
|
||||
if ($node->booking_partner_id != 0) {
|
||||
$partner = db_query("Select booking_partner_id from {booking_person} where nid = :nid", array(
|
||||
|
@@ -641,7 +641,7 @@ function booking_csv_report() {
|
||||
//keep a list of any fields that we need to handle as dates
|
||||
$datetime_fields = array('booking_outflight_origin_ts', 'booking_outflight_destination_ts', 'booking_rtrnflight_origin_ts',
|
||||
'booking_rtrnflight_destination_ts', 'booking_timestamp', 'booking_flight_datetime_inbound', 'booking_flight_datetime_outbound');
|
||||
$number_only_fields = array('booking_postcode', 'booking_mobile', 'booking_phone');
|
||||
$number_only_fields = array('booking_postcode', 'booking_mobile', 'booking_phone', 'booking_guardian_phone', 'booking_guardian_phone_alt');
|
||||
|
||||
//this isn't required since we already have the info directly as a field
|
||||
//so there is no need to rewrite the ID field with a user-friendly description
|
||||
|
Reference in New Issue
Block a user