"Optional" (empty value) Not Working For URL

[Soupy]

I'm still encountering problems with this "optional" issue. If you look at this jsFiddle, http://jsfiddle.net/3vz6A/, I want to be able to have a valid url entered into the textbox. The url value must be optional. The plugin insists on validating an empty value and shows "Invalid URL" in the tooltip!

What a I doing wrong? I've tried using the "optional" parameter but that didn't help.

[albertpak]

I'm having same issue with email address - i need to make it optional

Added class="validate[custom[email]]", nothing

Added class="validate[optional,custom[email]]", nothing

What needs to be done to pass this on as an optional field?

[posabsolute]

will have a look tomorrow @Soupy

[albertpak]

Awesome :) Your help is very much appreciated, let me know if there's something I can help with.

[posabsolute]

okay so the problem is that you got a whitespace in your textarea, since there is a value it's not considered blank, I added a test for option (#524) in the tests folder

[Soupy]

@posabsolute Thanks for looking and patching this issue. However, I don't understand what you've done to address it.

I tried the latest version on my jsfiddle and it still invalidates a blank value. If I remove the blank space, it's all good. The thing is, the original version of the plugin also behaved this way, so I'm left wondering what it is that you'd done to the latest version?

Update: Oops..looks like my jsfiddle was always pointing to the master/lastest so the behavior described above is not accurate for what I thought was the "original version". That's the good news. The bad news is now my form validation takes much longer when I'm tabbing thru fields. I can't demonstrate this on the jsfiddle though. I definitely do not see this hesitation when I switch back to the previous version of the plugin.

[posabsolute]

hi @Soupy

I merged some new functionality so that might be it, when you switch tab, what do you do? attach detach? im currently moving the events into on()

for the blank space frankly im not sure what to do with that, not sure it warrant a trim() since you want to validate that someone is just entering whitespace into your field.

[Soupy]

@posabsolute I've been testing the latest version of your plugin. The one where you've moved "the events into on()". I'm experiencing new errors now that do not exist in your previous version. In particular, what I am attempting to do is enable/disable a "Save" button depending on if the form is valid or not. The button is initially disabled and is supposed to stay disabled until the form validates at which point it should become enabled.

To do this, I was using the onFieldFailure and onFieldSuccess options as follows:

$('#frmOptions').validationEngine({
prettySelect: true
, usePrefix: 's2id_'
, autoPositionUpdate: true
,onFieldFailure: function(){
window.parent.jQuery(".ui-dialog").find('button#btnsave').attr('disabled', 'disabled');
}
,onFieldSuccess: function(){
if( $("#frmOptions").validationEngine('validate') )
window.parent.jQuery(".ui-dialog").find('button#btnsave').removeAttr('disabled');
}

This no longer works and throws the following error

Line: 148
Error: Unable to get property 'onValidationComplete' of undefined or null reference

I believe its related to the onFieldSuccess where I'm trying to check to see if the form is valid. If I remove that if() check and put an alert, I see the alert message. So, can you tell me what is the correct way to get the functionality that I need for this form?

Thanks again for your assistance.