In-Portal Issue Tracker - In-Portal CMS
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Type: | Reproducibility: | Date Submitted: | Last Update: |
224 | [In-Portal CMS] Front End | bug report | always | 2009-08-13 02:40 | 2009-10-03 07:57 |
|
|||||
Reporter: | alex | Platform: | |||
Assigned To: | alex | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 5.0.0 | ||
Product Build: | Resolution: | fixed | |||
ETA: | none | Fixed in Version: | 5.0.1 | ||
Reference: | |||||
Change Log Message: | |||||
Estimate Points: | 0 | ||||
|
|||||
Summary: | 0000224: Password validation logic change | ||||
Description: |
Currently when there is an error in one of Password or VerifyPassword field we set it in both fields. This looks very strange in cases, when form field validation is made one by one (using ajax). Example: I type "ab" in Password field and get "password too short" message in both fields. Same with "passwords don't match" error. I propose to set all errors except "don't match" into Password field only, but when passwords don't match, then set this error to VerifyPassword field only, because it doesn't match original Password field and not otherwise. |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: | |||||
|
|||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2009-10-03 07:57 | administrator | Note Added: 0000779 | |||
2009-10-03 07:57 | administrator | Status | resolved => closed | ||
2009-08-13 02:44 | alex | Fixed in Version | => 5.0.1 | ||
2009-08-13 02:44 | alex | Target Version | => 5.0.1 | ||
2009-08-13 02:43 | alex | Note Added: 0000315 | |||
2009-08-13 02:43 | alex | Status | active => resolved | ||
2009-08-13 02:43 | alex | Resolution | open => fixed | ||
2009-08-13 02:43 | alex | Assigned To | => alex | ||
2009-08-13 02:43 | alex | Changeset attached | 5.0.x r12279 | ||
2009-08-13 02:40 | alex | New Issue |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|