read the paragraph on the AUTH_PROFILE_MODULE in james blog.
especially understand you're pointing it at a modelname, but that it
knows its a model
caught me out once upon a time and might be your issue.
Matt
On Jul 13, 3:57 am, Brent wrote:
> Unfortunately, no matter
if i can extend the user model, anybody should be able to.
i followed james bennett example.
in fact most of the clever stuff i do came from his tuts
http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-model/
at this point, i'd suggest a clean virtualenv, with a single app,
I'm using python manage.py runserver, and I have restarted it dozens
of times.
On Jul 12, 8:58 pm, Micky Hulse wrote:
> On Tue, Jul 12, 2011 at 7:57 PM, Brent wrote:
> > Unfortunately, no matter what kind of path I put for
> > AUTH_PROFILE_MODULE, the
On Tue, Jul 12, 2011 at 7:57 PM, Brent wrote:
> Unfortunately, no matter what kind of path I put for
> AUTH_PROFILE_MODULE, the same error appears.
I don't know your setup, but have your tried restating Apache? That's
probably a stupid question/suggestion, but maybe worth a
Unfortunately, no matter what kind of path I put for
AUTH_PROFILE_MODULE, the same error appears.
On Jul 12, 5:51 pm, Andre Terra wrote:
> As the traceback helpfully states,
>
> Exception Type: SiteProfileNotAvailable at /profile/Exception Value:
> Unable to load the
As the traceback helpfully states,
Exception Type: SiteProfileNotAvailable at /profile/Exception Value:
Unable to load the profile model, check AUTH_PROFILE_MODULE in your
project settings
Good idea. Unfortunately, I tried that, but it results in a
SiteProfileNotAvailable error:
http://dpaste.com/567421/
On Jul 12, 3:15 pm, Andre Terra wrote:
> Instead of using get or create, why not setting up a post_save signal
> for the User model so that users always
Instead of using get or create, why not setting up a post_save signal
for the User model so that users always have a profile associated with
them?
Cheers,
Andre
On 7/12/11, Brent wrote:
> Thanks for the help guys.
>
> Micky, that tutorial looks very good. I think I almost
Running syncdb again didn't seem to fix it. I tried deleting the
database entirely, and starting from a new database, but that also
didn't work.
On Jul 12, 2:28 pm, Shawn Milochik wrote:
> On Tue, Jul 12, 2011 at 5:26 PM, Brent wrote:
> > Thanks for the
On Tue, Jul 12, 2011 at 5:26 PM, Brent wrote:
> Thanks for the help guys.
>
> Micky, that tutorial looks very good. I think I almost have it
> working. Just one more error:
>
> http://dpaste.com/567361/
>
Looks like maybe you didn't run syncdb after adding something to
Thanks for the help guys.
Micky, that tutorial looks very good. I think I almost have it
working. Just one more error:
http://dpaste.com/567361/
Andre, thanks for mentioning Pinax. I'll give it a shot if this
doesn't work out. I have a year of python experience, but I haven't
written anything
This tutorial helped me:
http://www.turnkeylinux.org/blog/django-profile
Note: The above tutorial uses an FK to User model... The Django docs
suggest a OneToOne field.
Hope that helps.
Micky
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
On Tue, Jul 12, 2011 at 2:51 PM, Brent <brentba...@gmail.com> wrote:
> Hi,
>
> Does anyone know of a simple, working example of custom user profile
> fields?
>
> I want to have a custom field, say, "favorite color," which is unique
> to each user.
https://docs.djangoproject.com/en/1.3/topics/auth/#storing-additional-information-about-users
Everything you should need is in here. Once you have something started I
can probably help out if you have any specific questions.
Also, as long as you have a one-to-one field there's really no need to
Hi,
Does anyone know of a simple, working example of custom user profile
fields?
I want to have a custom field, say, "favorite color," which is unique
to each user. Then I want users to be able to login, and be taken to a
page called "profile" that displays that custom fi
15 matches
Mail list logo