Changing jQuery validation on checkout.php causing "Please Wait" to hang...

http://www.ledwarehouseuk.com/LED-Lights-Bulbs.php?lbid=420 (Add to Basket > Checkout > Fill in Details > Click "Continue")

checkout.php attached.

EDIT: In IE we also note that, despite unticking the "Required" checkbox for 'State' and 'State_2', it won't let us past the jQuery validation for those fields. Could this be related to the problem?

Would appreciate your help. Thank you.
NJ

I have asked Ray to take a look at this, I will let you know when I have more information.

Thank you Jason. We did nothing other than edit the jQuery Validation on this page via WebAssist > Forms > jQuery Validation so, again, I'm at your mercy with regard to what has happened here. Hoping Ray can identify the issue.

Thank you.
NJ

Sorry to resurrect a 6 month old thread, but I wondered if you figured out this problem.
I have the exact same thing happening to me right now after using the JQuery Validation to update a page created by the checkout wizard.

The checkout.php page was passing validation no matter what. Even with all blank fields. So I opened the JQ Validation (WA > Forms > JQ Validation) and clicked OK. That stripped out several lines at the bottom and now I get the spinning wheel "Please Wait..." It goes nowhere.

Not sure if this adds anything but I do get a console error on this page when checking the "Same As Billing" checkbox.

TypeError: el is null
	
if (el.tagName == "SELECT") {

It's referencing somewhere around line 300 on the paymentoptions.js page, created for a Payments Advanced checkout.
The link to that page is one of the things that is stripped out when running the JQ Validation update.

function wa_getFieldValue(el) {
  if (el.tagName == "SELECT") {
	return el.options[el.selectedIndex].value;
  } else {
	return el.value;
  }
}

Thanks
TroyD

Hi Troy,

I'm afraid this is just one of the weird things that eCart does now and again - removing code, causing errors in other areas of code. We had Ray / Jason resolve it for us because there was no rhyme nor reason to it but I couldn't honestly tell you what they did because it was way above our heads. It certainly wasn't anything we were doing wrong though - we were just making changes to the jQuery validation via the wizard and it would subsequently wreck other areas of our page.

Tread with care is all I can say and always make a copy of your page when it WAS working, prior to making any changes. It's not a great way to have to work but it's the only solution sometimes when using WebAssist extensions even if it is just to prove that you're not going mad!

Good luck.
NJ