ur help.
> Gaurav Talwar
>
> warnings:
> Use of uninitialized value in numeric lt (<) at
> /Embperl/Form/Validate.pm line 492.
> Use of uninitialized value in concatenation (.) or string at
> /Embperl/Form/Validate.pm line 392.
> Use of uninitialized value in hash element
On Wed, Oct 11, 2006 at 04:35:04PM +0200, Gerald Richter wrote:
> > Line 362 of Embperl/Form/Validate.pm
> >
> > my $default_language = $pref -> {default_language};
> >
> > should be
> >
> > my $default_language = $pref -> {default_language} ||
> > $self->{default_language} ;
> >
>
> Yes, thi
> Line 362 of Embperl/Form/Validate.pm
>
> my $default_language = $pref -> {default_language};
>
> should be
>
> my $default_language = $pref -> {default_language} ||
> $self->{default_language} ;
>
Yes, this make sense. It's updated in the SVN.
>
> But it doesn't say how one should form th
I've been trying out Embperl::Form::Validate, (Embperl version 2.2.0)
and I've found what appears to be a bug with error messages.
If one does not give a $pref argument, and one does not give -msg values
in the RULES array, then all you get for an error message is the id
value of
without 8-bits, I believe the logic needs to be
> reversed - what isn't legal. I much prefer to do the check the way
> Embperl::Form::Validate does it, but I have the advantage of not
> having to support non-ASCII email addresses.
I've check it without 8-bits, but without succ
sed - what isn't legal. I much prefer to do the check the way
Embperl::Form::Validate does it, but I have the advantage of not having
to support non-ASCII email addresses.
Of course, you could always try saying IE isn't supported. ;>
Ed
On Mon, 3 Apr 2006, Florian 'cit&#
Hello list,
I've another problem! With Embperl::Form::Validate I generate a
javascript and check if the e-mail address is valid. With firefox and
mozilla it works very well, but the internet explorer (6.0.2) always
say the e-mail address is not valid. Is the generated Javascript
incompa
>
> Is it possible to use a different set of rules for form
> validation depending on which of several submit buttons on
> the form were pressed?
> I'm guessing no. It seems I have to have Form::Validate do
> the least common denominator checking, then do any furth
Is it possible to use a different set of rules for form validation
depending on which of several submit buttons on the form were pressed?
I'm guessing no. It seems I have to have Form::Validate do the least
common denominator checking, then do any further processing server side
afte
>
> How can i in embperl 2.0b8 with Validate module check, if some rule
> key ('user' in my example) is giving an error or not?
>
You need to use validate instead of messages:
use Embperl::Form::Validate ;
$validate = Embperl::Form::Validate->new();
$validate->
Hi,
How can i in embperl 2.0b8 with Validate module check, if some rule
key ('user' in my example) is giving an error or not?
### script start ###
[-
use Embperl::Form::Validate ;
$validate = Embperl::Form::Validate->new();
$validate->add_rule([-key=>'user', -msg=
>
> After the form is validated, if it is successful, there are other
functions
> I would like it to call. For example, I want to disable the "Submit"
button
> after it is pressed, as to prevent duplicate submissions. Is there a way
to
> do this using form validate?
&g
Hi,
After the form is validated, if it is successful, there are other functions
I would like it to call. For example, I want to disable the "Submit" button
after it is pressed, as to prevent duplicate submissions. Is there a way to
do this using form validate?
My form has several co
> As soon as I specify more than one or two tests the apache child
> begins to fill my memory quite fast and spams my browser with
> megabytes of output while doing so, which effectively forces me
> to kill both of them. I tried with Embperl 2.0b8 and with
> yesterdays CVS, the behaviour is identic
Hi,
today I tried out Form::Validate on my Apache 1, perl 5.8 installation.
The features look really great, but I have one problem:
As soon as I specify more than one or two tests the apache child
begins to fill my memory quite fast and spams my browser with
megabytes of output while doing so
16, 2002 at 08:34:34AM +0200, Gerald Richter wrote:
>
>
> > there seems to be a bug in the way Embperl::Form::Validate generates the
> > client-side javascript code for the radio inputs. The JS code is using
> > "value" property, which is not accurate for a Radio ob
> there seems to be a bug in the way Embperl::Form::Validate generates the
> client-side javascript code for the radio inputs. The JS code is using
> "value" property, which is not accurate for a Radio object.
>
Yes, radio buttons not supported so far, since they hav
there seems to be a bug in the way Embperl::Form::Validate generates the
client-side javascript code for the radio inputs. The JS code is using
"value" property, which is not accurate for a Radio object.
ilia.
-
To u
Esh :-)
When all else fails, try the obvious, eh? Thanks!
Justin
> -Original Message-
> From: Gavin Carr [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 12, 2002 9:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Form Validate Error
>
>
> On Mon, Aug 12,
On Mon, Aug 12, 2002 at 09:18:27PM -0400, Justin M. Harrison wrote:
> Rules.pm:
>
> sub loginform {
> return([
> [-key => 'username',
> -name => 'username'
Missing comma. :-)
> -msg => "Username was not entered",
> required=>1.
> -msg => "Username was too short",
>
M. Harrison [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 12, 2002 9:18 PM
> To: [EMAIL PROTECTED]
> Subject: Form Validate Error
>
>
> Hi,
>
> I am attempting to validate a submitted form via code called
> in an imported object perl module.
>
> This is
Hi,
I am attempting to validate a submitted form via code called in an
imported object perl module.
This is the error I am receiving:
ERR: 24: Error in Perl code: Can't locate object method
"validate_Username was not entered" via package
"Embperl::Form::Validate::Default&
22 matches
Mail list logo
