We're trying to track down a really unusual issue on the product page. It's probably self-inflicted. But we don't know how to locate the cause.

If a product page shows variants, and the shopper clicks add-to-cart without setting the variant selections first, the validation fires. Exactly like it should.

But the submit on the buyproductdialog form still got fired. And that throws an exception because the product ID wasn't included in the postback. So we wind up with a huge amount of this error in our error log:



I'm trying to debug this in Chrome. And I'm terrible at it, this javascript stuff is all new to me. I can see in the Network tab where it -appears- to be TWO postbacks happening when I click the button. One to /AddToCart and one to the ID of product being viewed. I'm thinking there should only be one but I am not sure.

That's as far as I can get. I don't know how to tell where those postbacks get triggered in the page code. The initiator column just says 'main.js' which tells me nothing.

Any suggestions? Here's what it says in my Network tab after clicking the add-to-cart button:

Capture.JPG (30kb) downloaded 3 time(s).

Were you testing on a variant product and making the validation fire i.e. not picking a required variant before clicking add-to-cart?

I'm fairly certain a customization somewhere has caused this.

I guess what I'm asking is if there's a way to tell exactly what javascript methods are fired when a button is clicked? Or is there a way to tell what routine made a specific <form> tag fire it's submit?

It has to be something attached to the button or the <form>. I just don't know how to track down stuff like this. There's so much js in the app I don't know where to begin to look.

Your screenshot does help a bit. At least it tells me which postback is the one that is SUPPOSED to be there. Now I just have to figure out why my 2nd postback is there.

Thanks Judy I'll give it a try