Anonymous | Login | Signup for a new account | 2024-03-28 11:16 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001095 | [In-Portal CMS] Front End | bug report | always | 2011-08-10 05:03 | 2011-09-19 16:08 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001095: Error messages are displayed on unrelated forms | ||||
Description |
I've noticed, that these forms: * login sidebox * subscribe to mailing sidebox * recommend site sidebox * forgot password page share same user object for data validation and processing. Because of it if error happens on one of this forms, then it will be shown on other fields, e.g. error on "Forgot Password" form in Email field is displayed on "Recommend Site" sidebox. I'm proposing to assign "special" to each of sideboxes so data don't get mixed, like <inp2:u.login .../> ; <inp2:u.subscriber .../> and <inp2:u.recommend .../> After that error will be raised, that there is no ID in request for mentioned above Specials. Then we need to change UsersEventHandler::getPassedID method to return current GUEST user's ID for these specials. |
||||
Additional Information |
Not obvious things, that were changed: 1. Unique field names were used on all forms, so instead of Email field being used everywhere now RecommendEmail, ForgotEmail, e.t.c. are used. This will help, when forms will be converted to AJAX approach using FormManager class. |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |