Proper form input error handling

[Barrett]

Related to Radio button in lieu of Select list in checkout screens.
http://extranet.mivamerchant.com/for...ad.php?p=81112

It seems to me that the merchant engine, api or whatever the heck it is should allow SMT modification of form input types and provide the same error handling etc.

I put a lot of work into making a custom OSEL screen once partly done at least thru the radio buttons - hooray and renders in stupid IE 6 and 7 ok, but then party is over when I find error handling tango uniform....@#$%@$#^

Current solution WCW to the rescue....

I really think generic input types concurrent with the new SMT paradigm should allow for this without 3rd party intervention.

[Brandon MUS]

Re: Proper form input error handling

What exactly is your error? I do wish Miva handled errors with more grace than "OMG Fatal error!". Another area that is annoying is on the BASK screen when you remove a product. If you refresh that screen, you get a nasty error because the basket line id no longer exists... I say that if it no longer exists, who cares?

[Barrett]

Re: Proper form input error handling

What exactly is your error? I do wish Miva handled errors with more grace than "OMG Fatal error!". Another area that is annoying is on the BASK screen when you remove a product. If you refresh that screen, you get a nasty error because the basket line id no longer exists... I say that if it no longer exists, who cares?

Error handling related to my aforementioned thread...
Maybe it would be accurate to say handling stupid user error when they don't check a box they should an attempt to submit form in general.

In specific scenario it was changing the OSEL page ship and pay methods from Select menu style to radio buttons - proper error trap was not possible without a 3rd party mod per WCW and we got his mods in place now at our beta site.

SMT should allow for variations of input style

[Brandon MUS]

Re: Proper form input error handling

I went through that same problem when I made the changes you did.

My opinion on it is that this isn't a SMT problem, but a Miva core problem. When Miva tries to verify the user's selection of shipping and payment methods, it blows up. What would be better is if it created an error message like it does when it validates the user's address. A simple message that said "Please select a shipping method below" without changing the screen would be great.