drupal/booking
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

tweak to phone number handling in CSV

Browse Source
This commit is contained in:
Nathan Coad
2016-06-18 19:16:35 +10:00
parent 5a4ee8054f
commit 1d4af9ac39
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
booking.regn_form.inc
View File

@@ -1260,6 +1260,8 @@ function booking_form_submit($form, &$form_state)
function _booking_form_submit_post_triggers($node) function _booking_form_submit_post_triggers($node)
{ {
global $event; 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 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) { if ($node->booking_partner_id != 0) {

2
booking.reports.inc
View File

@@ -641,7 +641,7 @@ function booking_csv_report() {
//keep a list of any fields that we need to handle as dates //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', $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'); '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 //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 //so there is no need to rewrite the ID field with a user-friendly description