CoreCommerce: Address attribute handled w/ Javascript?
Permalink
Hey all,
I'm a seasoned php developer with plenty of javascript knowledge, but I can't seem to wrap my head around this. In CoreCommerce, on the 'billing info' page where you enter your name and address (using the 'address' attribute) I'm having problems.
Works OK in firefox/chrome - but like always, its f*cked up in IE. Either the form won't submit, or the 'States' field won't populate... which after looking into the code, looks like thats generated w/ javascript??? Anyways, when trying to submit the form, all I get back is the "address field required" error.
Anyone have any similar problems or know of any fixes? I think the States field simply isn't getting passed - but since its an attribute, its near impossible to modify.
THanks in advance,
Jon
I'm a seasoned php developer with plenty of javascript knowledge, but I can't seem to wrap my head around this. In CoreCommerce, on the 'billing info' page where you enter your name and address (using the 'address' attribute) I'm having problems.
Works OK in firefox/chrome - but like always, its f*cked up in IE. Either the form won't submit, or the 'States' field won't populate... which after looking into the code, looks like thats generated w/ javascript??? Anyways, when trying to submit the form, all I get back is the "address field required" error.
Anyone have any similar problems or know of any fixes? I think the States field simply isn't getting passed - but since its an attribute, its near impossible to modify.
THanks in advance,
Jon
We've been working with eCommerce for a bit and haven't seen this particular issue. We've used it on IE 6,7,8, as well as recent flavors of firefox, safari and chrome. However, that's with version 1.5.1. We'll see what happens when we upgrade. What version are you on and which version of IE?
Currently on version 1.6.5, but this had happened w/ all previous versions too.
Found out the problem was with a conflicting javascript library I had included on the page. But still, for an e-commerce system, that seems pretty brittle if it can be broken simply by an unfriendly piece of javascript (or what if a client doesn't have javascript enabled?)
Found out the problem was with a conflicting javascript library I had included on the page. But still, for an e-commerce system, that seems pretty brittle if it can be broken simply by an unfriendly piece of javascript (or what if a client doesn't have javascript enabled?)
I have this problem also. Still looking for a solution.
