I really don´t know where to submit it. And as I recall, I should test
it with a test tool ( like qUnit) before, shouldn´t I?
If I don´t, I´d be pleased to submit it.
On Sep 29, 7:08 pm, James wrote:
> You wanna go ahead and submit something in the Validation plug-in bug
> tracker for this (if i
You wanna go ahead and submit something in the Validation plug-in bug
tracker for this (if it doesn't exist)?
On Sep 29, 10:31 am, Thiago Miranda de Oliveira
wrote:
> I thought in cache too, but I think the plugin author implemented this
> but didn´t test it on such a particular case.
>
> On Sep
I thought in cache too, but I think the plugin author implemented this
but didn´t test it on such a particular case.
On Sep 29, 5:22 pm, James wrote:
> Yes, I've did the change you mentioned and it did work as expected
> afterwards.
> I'm also curious as to what the purpose of it is also. I have
Yes, I've did the change you mentioned and it did work as expected
afterwards.
I'm also curious as to what the purpose of it is also. I haven't
really delved into it but it looked like a message cache.
On Sep 29, 3:57 am, Thiago Miranda de Oliveira
wrote:
> My code is like that:
> rules: {
>
My code is like that:
rules: {
'email_address': {
required: true,
email: true,
rangelength: [3, 60],
remote: {
url: 'someurl.php',
dataType: 'json',
type:
I've done a quick test on it on 1.5.5 and I'm experiencing the
duplicate message issue also using the following message options:
remote: function() {
// $("#email") is the input field for the email address
return $("#email").val()+' already exists';
}
remote: function(email) {
return
Could you provide some code on how you're setting the error message
"... already exists"?
On Sep 28, 7:49 am, Thiago Miranda de Oliveira
wrote:
> Hi.. I´ve upgraded my validate plugin to the 1.5.5 and I was having a
> problem:
> I have an email that needs to be checked if it already exists by aj
7 matches
Mail list logo
