Validation on File Field with DA Update page.

Hello,

Extensions in use on this one are: Data Assist 2, Universal Email 4 (File Manipulation) and Form Toolkit 1.

The issue:

File fields with File Type Validation Applied fail on update if there is not a file selected manually.

The file fields are using the original value (from the hidden field as per DA GSG) to set the file name - this works before validation is applied to the form.

It would appear that the Validation Toolkit is not recognizing the default value from the file fields. File Extension Validation is bound to the following:

$WAFV_Errors .= WAValidateFE(((isset($_FILES["filenamehere"]))?$_FILES["filenamehere"]["name"]:"") . "",".gif, .jpg, .jpeg, .png",true,13);

Here is one of the 6 file upload behaviours:

// WA_UploadResult1 Params Start
$WA_UploadResult1_Params = array();
// WA_UploadResult1_1 Start
$WA_UploadResult1_Params["WA_UploadResult1_1"] = array(
    'UploadFolder' => "../../images/headers/",
    'FileName' => "[FileName]",
    'DefaultFileName' => "".((isset($_POST["filenamehere"]))?$_POST["filenamehere"]:"")  ."",
    'ResizeType' => "0",
    'ResizeWidth' => "0",
    'ResizeHeight' => "0",
    'ResizeFillColor' => "" );
// WA_UploadResult1_1 End
// WA_UploadResult1 Params End

and the rest of it:

WA_DFP_SetupUploadStatusStruct("WA_UploadResult1");
if(isset($_POST["Update_x"])){
    WA_DFP_UploadFiles("WA_UploadResult1", "filenamehere", "0", "", "true", $WA_UploadResult1_Params);
}

Anyone seen this issue before or know of a resolution?
Thanks.

Andrew,

I think I get what your trying to do but correct me if I am wrong.

You have an update page where you have a file field but you also have, I am assuming, a hidden field to contain the value of the original file that will be the default if there is no new file uploaded, correct?

If that is the case, I would double check that when validating the file extension of your file field that you ensure that the selection can be left blank. That way it will only validate if there is an input/upload present in the field.

Happy New Year and Cheers,

Brian

Hi Brian,

Yes, in fact there are 6 files that could possibly be uploaded with this particular update form, and I am using (as per the GSG) the hidden field in order to set the default value for each file.

I will try the 'allow blank' solution, but should the hidden (default) value not get passed on so that it could validate against that instead?

Ok... I see what you are saying. But I think by allowing blank, it just means the form can pass with an empty input... I think it should still use the default if the input itself is empty.

If not, you could modify the update code slightly by hand by writing an "if" statement that checks if the input has a value and if the value has no string length, it would then revert to the default file.

Best regards,

Brian

Hi Brian,

Your solution has worked, it is just in my mind that I couldn't see the logic of allowing a blank field. It does make sense to allow blank as long as there is already a default value though. ;)

Thank you.