QuickForm and AOL account
| From: | Erik Heerlein | Date: | Fri, 12 Nov 2004 04:42:05 +0000 |
| Subject: | QuickForm and AOL account | ||
| Groups: | php.pear.general | ||
| Request: | Send a blank email to pear-general+get-15461@lists.php.net to get a copy of this message | ||
I'm using HTML_QuickForm on a page that presents the available shipping options that a customer can choose from. Everything works fine except for some people. For some people when they choose their preferred shipping method via a radio button and hit the submit button, the form fails to validate and the "required" rule throws an error. The form is presented again and displays the error, "Please choose a shipping method...".
The form acts like the user didn't make a selection and the user just hit the submit button when in fact the user did make a selection and their choice does show up in the $_POST superglobal so I know the browser did pass on the info.
The really weird thing is that this problem only appears to happen with people using AOL with a PC. One potential customer said she tried using AOL's browser, IE and Netscape and ran into the same problem all 3 times but she was signed on using an AOL account from her home computer. I have tried signing on using an AOL account and tried those same 3 browsers with no problems at all but I was using a Mac.
I don't think the issue resides with my implementation of HTML_QuickForm because if it was broken, the form would be broken for everybody, not just for some users.
And as far as I can tell, the only thing related to these errors is using AOL from a PC. I'm going to borrow a friend's PC laptop with an AOL account and try that from home to rule out any personal firewall issues that users may have.
If anybody with an AOL account and a PC and wants to test my theory go to www.pixiedustgifts.com, add an item into your shopping basket, enter in some address info, and then choose your shipping method. If you get passed that page and are presented with a summary of your order, then my AOL theory is incorrect and the problem lies elsewhere.
Anybody got any ideas? Thanks in advance.
- Erik Heerlein