search

samimave / car-pool

Automatically exported from code.google.com/p/car-pool
0 stars 0 forks source link

User Account page #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Users should be able to see their details on the myDetails page and edit 
them.

Estimated Time: 3 days

Original issue reported on code.google.com by parul2...@gmail.com on 13 Aug 2008 at 4:18

GoogleCodeExporter commented 9 years ago 
I have a made some classes which will make this easier for whoever takes it on.
User, UserManager and UserFactory

Original comment by terrasea on 13 Aug 2008 at 5:48

GoogleCodeExporter commented 9 years ago 
I am going to claim this task. Will try to do it in the weekend or next week.

Original comment by parul2...@gmail.com on 13 Aug 2008 at 12:03

GoogleCodeExporter commented 9 years ago 
Users can see their own details now. Like James mentioned he had created the 
needed 
classes anyway so it was just a matter of calling user.whatever

He is going to be working on a way of updating the user data called 
updateUserDetails

Original comment by parul2...@gmail.com on 20 Aug 2008 at 9:09

GoogleCodeExporter commented 9 years ago 
User is able to see the rides they have offered in the myDetails page now.
But we need to be able to distinguish between offers and requests
eventually. Also we need sql query using matches table to find rides user
has accepted 

Defect: When the number of seats available drops to 0 the user is not able to 
see 
that offer in the offer table. This needs to be fixed.

Original comment by parul2...@gmail.com on 25 Aug 2008 at 3:40

GoogleCodeExporter commented 9 years ago 
Defect:
If I try and update my details and keep the same username I get a bunch of 
errors.
I assume this is due to the database only allowing unique usernames. You might
already be aware of this. I suggest that a user cant change their username after
registering.

Original comment by arlo.pho...@gmail.com on 7 Sep 2008 at 11:52

GoogleCodeExporter commented 9 years ago 
Fixed the above issue.  The user can't change their username and the correct 
method
to update their details is now being used.

The adding and removing of openids has some issues though.  If a user adds a 
openid
to their account the openid should be normalised if needed and authenticated. 
ie put
http:// on the front of it if it isn't there.  Also a user should not be able to
remove their last and remaining openid.  If they do this it will may make their
account unaccessable, due to there being no way for them to log back in, if 
they have
no password.

Original comment by terrasea on 23 Sep 2008 at 11:43

GoogleCodeExporter commented 9 years ago

Original comment by parul2...@gmail.com on 14 Oct 2008 at 8:58