Hi Edward

To access the entered value in a CForm I use the following construct based
on a personal server side javascript function.

<fd:field id="form_bis" required="false">
        <fd:datatype base="date">
                ...     
        </fd:datatype>
        <fd:validation>
                <fd:javascript>
                        return checkFormInputDate(widget);
                </fd:javascript>
        </fd:validation>
</fd:field>


function checkFormInputDate (widget, regExpValidation,
regExpValidationError)
{
        
        var enteredValue = new
String(cocoon.request.getParameter(widget.getRequestParameterName()));
        ...
}

Raffaele

-----Ursprüngliche Nachricht-----
Von: Edward Elhauge [mailto:[email protected]] 
Gesendet: Mittwoch, 4. Februar 2009 02:05
An: [email protected]
Betreff: [?? Probable Spam] More control over Cform Date Conversion

Hi,

I've run into a problem where my users want more detailed control over
Date field validation. In the version that we're running (2.1.8)
we don't have a "lenient" attribute for base="date" widgets.

So the user can type in "33/60/9z" as a date, which get converted into
"10/30/2011". Not what was expected.

What I'd like would be to a small:
  <fd:validation> <fd:javascript>
  ...
  </fd:javascript> </fd:validation>
section to throw an error in those cases.

Unfortunately this.value inside that javascript callback is already in a
Date format.

My question is:
  How do I get access to the users original text input
  within the fd:validation section?

  If there is no way to get access to the raw text, do I need to write
  my own validator to replace "FormattingDateConvertor" ?

-- 
        Edward Elhauge <[email protected]>
"The right dose differentiates a poison and a remedy." -- Paracelsus (1493 -
1541)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to