View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002902 | OXID eShop (all versions) | 1.05. Users | public | 2011-05-19 11:45 | 2012-03-09 18:19 |
| Reporter | mkr | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Product Version | 4.4.8 revision 34028 | ||||
| Summary | 0002902: MustFillFields and regestration | ||||
| Description | We have some problems on regestrations wit house numbers and MustFillFields. If a customer live in a street without a house number, they like to enter a 0 as house number, but this results in a 'fillout neccessary fields' warning. How to handle these scenario? Instruct the customer to use an another character like '-'? -- possible problems with delivery company Disable the housenumber MustFillFields? -- i do not like this Or to change the validation code? -- but where? | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
|
|
Reminder sent to: mkr Hi, What is the default value in this case, when customer doesn't have house number? Because probably, when paying with Credit Card or PayPal, the address should match on both sides. So in this case it's important what user would insert - "0" or "-" or something else. Most likely it should be the same as is inserted in Credit Card address info or PayPal. |
|
|
The default value is an empty string, but this is not compatible with the MustFillFields function. The value '0' is handled in same way as an empty string and this is the current problem. I think to handle empty streetnr strings is to disable MustFillFields for oxstreetnr. |
|
|
Reminder sent to: mkr Hi, eShop allows registration with "-" instead the Street name and the house number. We think that this is enough to handle such cases properly. So no more changes required from our side. |
