nevermind, i figured it out. thanks anyway
On Jun 22, 5:11 pm, raj wrote:
> I think I'm starting to get the hang of it a little. I was able to
> extract the data from the profile and set it as the initial value.
> From what I understand, you would like me to set each user
I think I'm starting to get the hang of it a little. I was able to
extract the data from the profile and set it as the initial value.
>From what I understand, you would like me to set each user field one
at a time, but if I have 20-30 fields that need to be updated at once,
I'm at a loss. The way
On Wed, Jun 22, 2011 at 10:14, raj wrote:
> If I didn't have the url
> set up in this manner, how would I manage to extract the userprofile?
If you have the "AuthenticationMiddleware" activated you would use request.user
This returns a User object, which you then can use to
This is an interesting way of doing it. I don't have it set up so that
every user has their own url that contains their db id. Django checks
to see if the user is authenticated or not. If I didn't have the url
set up in this manner, how would I manage to extract the userprofile?
I was seeing
I'd advise you to
read
https://docs.djangoproject.com/en/1.3/topics/auth/#storing-additional-information-about-users.
So, create a separate model for the profile, which can be edited by the user
once he is logged in.
--
You received this message because you are subscribed to the Google
On Wed, Jun 22, 2011 at 08:28, raj wrote:
> I'm trying to create an update_profile form. This form will be able to
> update extended user information that is not in the original form.
>
> So, I have a form that allows you to create an account. There a lot of
> other fields
I'm trying to create an update_profile form. This form will be able to
update extended user information that is not in the original form.
So, I have a form that allows you to create an account. There a lot of
other fields that aren't listed in this form. The rest of these fields
will be found
7 matches
Mail list logo