3,035
edits
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
* [http://lxr.mozilla.org/mozilla/source/webtools/partytool/README README] | * [http://lxr.mozilla.org/mozilla/source/webtools/partytool/README README] | ||
= Issues | = New Issues = | ||
* After the invite is sent out, user goes to register page, but then has no where to go. The original invite is lost, somehow. Also, if you send an invite out to an existing user, why shouldn't have to re-register, and they should also retain the invite context (be added to the party when they do log in). | |||
* Session method should be database, not php. See line: 78 | * Session method should be database, not php. See line: 78 | ||
78 define('CAKE_SESSION_SAVE', 'php'); | 78 define('CAKE_SESSION_SAVE', 'php'); | ||
= Wil's Points = | |||
* <strike>/config/database.php shouldn't be in the repository. IT prefers a .default or -dist file. (Same goes for config/bootstrap.php if you expect IT to change values in it)</strike> | * <strike>/config/database.php shouldn't be in the repository. IT prefers a .default or -dist file. (Same goes for config/bootstrap.php if you expect IT to change values in it)</strike> | ||
| Line 23: | Line 25: | ||
* <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> | ||
* When I created the party I did not choose "Invite only," however, when I go to the "Invite a guest" option it says "Since your party is invite only..." | * <strike>When I created the party I did not choose "Invite only," however, when I go to the "Invite a guest" option it says "Since your party is invite only..."</strike> | ||
* /register/ is a 404, but is linked to in the code (line 333 in controllers/party_controller.php - might be elsewhere too) | * <strike>/register/ is a 404, but is linked to in the code (line 333 in controllers/party_controller.php - might be elsewhere too)</strike> -- haven't seen this. An invite code might be null and cause this in the controllers, but I didn't produce that situation | ||
* After updating a profile, the user is logged out | * <strike>After updating a profile, the user is logged out</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. | * 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. | ||
| Line 33: | Line 35: | ||
* 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 | * 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 | ||
* going to /party/view/<number> and clicking "Count me in!" will create rows in the database for parties that don't exist | * <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. | * When viewing a party that is invitation only, there is no way for someone to tell that they have to be invited. | ||
edits