Thanks Karen - I think I will start doing that from now on.
Thanks everyone else - For now I'm just rolling back a bit before I
started getting the error and go from there. It seems that my project
scope has changed a bit midstream anyway so I guess this really isn't
the end of the world. If I do
On Sun, Jun 7, 2009 at 5:42 PM, grElement wrote:
>
> Alex
>
> Sorry I wasn't more clear, but I wasn't suggesting that the fact I'm
> getting the error is a bug, but it seems as though this error message
> results in an uncaught error and that is something they are working on
> already - see this
Alex
Sorry I wasn't more clear, but I wasn't suggesting that the fact I'm
getting the error is a bug, but it seems as though this error message
results in an uncaught error and that is something they are working on
already - see this http://code.djangoproject.com/ticket/6442
Here is the entire t
Paul
Actually this is what I already have in all my model definitions - as
suggested in some of the documentation and it's been working so far on
several different projects.
def __unicode__(self):
return u'%s' % (self.title)
Please also note that no changes were made to
Hi,
I just got this error a few days back. It was resulting from a
OnetoOne model referencing 'user' in one of the admin display_fields.
I thought user would resolve to the __unicode__ value of the user
model, for some reason (django bug?) it does not.
THE FIX
This is more like a patch,
On Sun, Jun 7, 2009 at 5:53 AM, Daniel Roseman <
roseman.dan...@googlemail.com> wrote:
>
> On Jun 7, 9:33 am, grElement wrote:
> > Yeah, I couldn't figure it out either since the error message is not
> > so helpful and it seems that this is actually a django bug that they
> > are currently workin
On Jun 7, 9:33 am, grElement wrote:
> Yeah, I couldn't figure it out either since the error message is not
> so helpful and it seems that this is actually a django bug that they
> are currently working on, but according to the documentation of the
> error reporting bug it should be coming from my
Yeah, I couldn't figure it out either since the error message is not
so helpful and it seems that this is actually a django bug that they
are currently working on, but according to the documentation of the
error reporting bug it should be coming from my view file. Weird thing
is I've used this sam
On Sat, Jun 6, 2009 at 11:05 PM, grElement wrote:
>
> I found the tickets regarding this error on the bug reports and
> noticed that it comes up when there is something wrong with your view,
> but I can't seem to find anything off. Here is my view.py in that app.
> Weird thing is I'm just copying
I found the tickets regarding this error on the bug reports and
noticed that it comes up when there is something wrong with your view,
but I can't seem to find anything off. Here is my view.py in that app.
Weird thing is I'm just copying this over from another project and it
was working fine there
10 matches
Mail list logo
