mind you they may not be there as such in the future if I ever get finish the next version
Please do. I’ll see if I can incorporate it from your patch.
mind you they may not be there as such in the future if I ever get finish the next version
But they are used in eFormOnValidate, so if the event system of eForm won’t be changed in future they should stay. I’ll try to get them ’named’ and send you the diff or the code.
177c177
< $vMsg[count($vMsg)]=$_lang['ef_failed_vericode'];
---
> $vMsg['vericode']=$_lang['ef_failed_vericode'];
191c191
< $rMsg[count($rMsg)]="$desc";
---
> $rMsg[$name]="$desc";
195c195
< $value = validateField($value,$fld,$vMsg,$isDebug);
---
> $value = validateField($value,$fld,$vMsg,$isDebug,$name);
206c206
< $vMsg[count($vMsg)]=$desc . $_lang["ef_invalid_number"];
---
> $vMsg[$name]=$desc . $_lang["ef_invalid_number"];
215c215
< $vMsg[count($vMsg)]=$desc . $_lang["ef_invalid_date"];
---
> $vMsg[$name]=$desc . $_lang["ef_invalid_date"];
223c223
< $vMsg[count($vMsg)] = isset($formats[$name][4]) ? $formats[$name][4] : $desc . $_lang["ef_invalid_email"];
---
> $vMsg[$name] = isset($formats[$name][4]) ? $formats[$name][4] : $desc . $_lang["ef_invalid_email"];
229c229
< $vMsg[count($vMsg)]=$desc . $_lang['ef_upload_exceeded'];
---
> $vMsg[$name]=$desc . $_lang['ef_upload_exceeded'];
232c232
< $rMsg[count($rMsg)]=$desc;
---
> $rMsg[$name]=$desc;
235c235
< if( substr($fld[5],0,5)!="#LIST" || validateField($_FILES[$name]['name'],$fld,$vMsg,$isDebug) )
---
> if( substr($fld[5],0,5)!="#LIST" || validateField($_FILES[$name]['name'],$fld,$vMsg,$isDebug,$name) )
883c883
< function validateField($value,$fld,&$vMsg,$isDebug=false){
---
> function validateField($value,$fld,&$vMsg,$isDebug=false,$name=''){
893c893
< $vMsg[count($vMsg)] = "$desc »" . $_lang['ef_error_validation_rule'];
---
> $vMsg[$name] = "$desc »" . $_lang['ef_error_validation_rule'];
1005c1005
< $vMsg[count($vMsg)] = $errMsg;
---
> $vMsg[$name] = $errMsg;<?php
function validationplaceholder(&$fields, &$vMsg, &$rMsg) {
foreach ($rMsg as $rField => $rMessage) {
$fields['validate_'.$rField] = 'Please fill this field!';
}
foreach ($vMsg as $vField => $vMessage) {
$fields['validate_'.$vField] = 'Field not valid!';
}
return true;
}
// Return empty string
return '';
?>
No, this is for historic reasons only,.. targeted to change in the future, mind you they may not be there as such in the future if I ever get finish the next version.
KP
Your observations seem accurate to me. In some cases a snippet/plugin pioneer moved on and notified the community about it (DirectResize and YAMS). I wish that would be the case here too.
It seems to me that eForm, like Jot, MaxiGallery and Ditto, reached a plateau some time ago - the developers responded to initial concerns and suggestions, something imperfect but adequate for the great majority of cases resulted [...] Given that some of the original developers have moved on or are unlikely to develop things further for whatever reason, support and development come down to others in the community [...]