Re: Field available via Django shell but not via web application (crossposted from StackOverFlow)

You said you are using django.contrib.auth.models.User as your User model, but that doesn't have a "foos" property. Can you share the models that you are using? Are you creating a subclass User that extends django.contrib.auth.models.User and adds foos and a ForeignKey? Is foos a ManyToManyField, OneToOneField, or just a ForeignKey to a Foos model which has a name property?

Thanks,

Furbeenator

On Wed, Nov 2, 2011 at 8:27 AM, Jordan <jordanthecoder@gmail.com> wrote:

Yes, it does work in runserver, as might be expected since runserver
uses exact same environment as the shell.

So that established, how can I fix it?

On Nov 1, 9:04 pm, Andy McKay <a...@clearwind.ca> wrote:
> Is this using the Django built in runserver or some other way of serving
> pages? If not try using runserver.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.