190
edits
Webtools:Mozparty: Difference between revisions
Jump to navigation
Jump to search
m
→Wil's Points
No edit summary |
m (→Wil's Points) |
||
| Line 25: | Line 25: | ||
* <strike>Going to /user/activate/<random characters> inserts new rows in the database</strike> | * <strike>Going to /user/activate/<random characters> inserts new rows in the database</strike> | ||
* '''When updating a profile, if the passwords don't match the error just says "There was an error in your submission..." but doesn't say what it was''' -- There is still a problem here. There is a JS alert, then it'll just change it without any error now. | * <strike>'''When updating a profile, if the passwords don't match the error just says "There was an error in your submission..." but doesn't say what it was''' -- There is still a problem here. There is a JS alert, then it'll just change it without any error now.</strike> - fixed (as well as the other validation issues below). There was an invalidate() missing. | ||
* <strike>When updating a profile, if input is "<'name" it is saved/returned as "<'name". Each time the profile is updated, the entities are re-encoded again.</strike> | * <strike>When updating a profile, if input is "<'name" it is saved/returned as "<'name". Each time the profile is updated, the entities are re-encoded again.</strike> | ||
| Line 35: | Line 35: | ||
* <strike>After updating a profile, the user is logged out</strike> | * <strike>After updating a profile, the user is logged out</strike> | ||
* <strike>When updating a profile, if a password is entered into the first box but not the second (or the second doesn't match), the password overwrites the saved password in the database in plain text. | * <strike>When updating a profile, if a password is entered into the first box but not the second (or the second doesn't match), the password overwrites the saved password in the database in plain text. -- '''This no longer produces an overwrite in plaintext, but it does not show an error of any sort, and takes the user back to their home page. It is a bad UI experience and should be fixed, IMO. This is pretty much the same issue as below.'''</strike> | ||
* <strike>When updating a profile, if a password is entered into the second box but not the first, the form continues submission, no updates are made, no errors are shown | * <strike>When updating a profile, if a password is entered into the second box but not the first, the form continues submission, no updates are made, no errors are shown -- '''Same problem as above. When passwords to not match you should stop submission and show an error.'''</strike> | ||
* <strike>going to /party/view/<number> and clicking "Count me in!" will create rows in the database for parties that don't exist</strike> | * <strike>going to /party/view/<number> and clicking "Count me in!" will create rows in the database for parties that don't exist</strike> | ||
* When viewing a party that is invitation only, there is no way for someone to tell that they have to be invited. -- '''This is still an issue -- a user really has no way of seeing "parties I've been invited to".''' | * When viewing a party that is invitation only, there is no way for someone to tell that they have to be invited. -- '''This is still an issue -- a user really has no way of seeing "parties I've been invited to".''' | ||