Apr 23rd, 2014, 12:34 PM
I have solved this problem but it took some finding.
I have a code hook in ft_update_submission,start. Although it appeared to be working there must have been a problem with it. However this problem was not flagged in edit_submission.php i.e.
Both $g_success and $g_message were being returned as NULL. Later in edit_submission.php there is a call thus:-
Because $failed_validation was true, the merge code here (I think) just kept adding the POST'd values to themselves and (I think) was causing the multiple slashes to appear.
I corrected my hook and everything behaved itself again
I wonder if this should be flagged up to Ben/Joe??
I have a code hook in ft_update_submission,start. Although it appeared to be working there must have been a problem with it. However this problem was not flagged in edit_submission.php i.e.
Code:
list($g_success, $g_message) = ft_update_submission($form_id, $submission_id, $request);
// if there was any problem udpating this submission, make a special note of it: we'll use that info to merge the current POST request
// info with the original field values to ensure the page contains the latest data (i.e. for cases where they fail server-side validation)
if (!$g_success)
{
$failed_validation = true;
}
Both $g_success and $g_message were being returned as NULL. Later in edit_submission.php there is a call thus:-
Code:
$grouped_fields = ft_get_grouped_view_fields($view_id, $tab_number, $form_id, $submission_id);
if ($failed_validation)
{
$grouped_fields = ft_merge_form_submission($grouped_fields, $_POST);
}
Because $failed_validation was true, the merge code here (I think) just kept adding the POST'd values to themselves and (I think) was causing the multiple slashes to appear.
I corrected my hook and everything behaved itself again
I wonder if this should be flagged up to Ben/Joe??