How to interpret error messages
12 views
Skip to first unread message
Rico
Mar 10, 2012, 2:31:16 AM3/10/12
to django...@googlegroups.com
I'm trying to learn Django and have been following several online tutorials hoping to understand how to create my own projects.
I'm having trouble interpreting the error messages that are given when I do something wrong. Unfortunately I don't seem to get much help when I try and find a solution via Google since I don't really know enough about Django to ask the right questions. Perhaps I can find help here?
I don't know where to start exactly - the code is spread out all over! Let's start with the error message:
http://dpaste.com/714463/
Clearly it's upset about how I've registered my Entry class. What is the problem and how do I fix it?
I'm having trouble interpreting the error messages that are given when I do something wrong. Unfortunately I don't seem to get much help when I try and find a solution via Google since I don't really know enough about Django to ask the right questions. Perhaps I can find help here?
I don't know where to start exactly - the code is spread out all over! Let's start with the error message:
http://dpaste.com/714463/
Clearly it's upset about how I've registered my Entry class. What is the problem and how do I fix it?
dummyman dummyman
Mar 10, 2012, 6:06:27 AM3/10/12
to django...@googlegroups.com
can u paste the file's contents ?
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/kzW8_UbAjKcJ.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Daniel Roseman
Mar 10, 2012, 8:36:07 AM3/10/12
to django...@googlegroups.com
Since you realize that the problem is in how you've registered the Entry class, don't you think it would be a good idea to show us how you're doing it in that admin.py?
--
DR.
Rico
Mar 10, 2012, 10:09:10 AM3/10/12
to django...@googlegroups.com
Since you realize that the problem is in how you've registered the Entry class, don't you think it would be a good idea to show us how you're doing it in that admin.py?--DR.
I've managed to solve the problem - it wasn't in the admin.py - it was with my models.py.
class Entry():
stuff
changed to:
class Entry(models.Model):
stuff
I don't understand what that did, but it was the root of my problem.
arapaho
Mar 10, 2012, 7:53:22 PM3/10/12
to Django users
That just says that your Entry class inherits from the Model class,
which is found in the models module. I am a relative noob also, and
found a hard copy Django book was my best initial source.
On Mar 10, 10:09 am, Rico <rico.cord...@gmail.com> wrote:
> > Since you realize that the problem is in how you've registered the Entry
> > class, don't you think it would be a good idea to show us how you're doing
> > it in that admin.py?
> > --
> > DR.
>
> I've managed to solve the problem - it wasn't in the admin.py - it was with
> my models.py.
>
> *class Entry():*
> * stuff*
> *
> *
> changed to:
>
> *class Entry(models.Model):*
> * stuff*
> *
> *
which is found in the models module. I am a relative noob also, and
found a hard copy Django book was my best initial source.
On Mar 10, 10:09 am, Rico <rico.cord...@gmail.com> wrote:
> > Since you realize that the problem is in how you've registered the Entry
> > class, don't you think it would be a good idea to show us how you're doing
> > it in that admin.py?
> > --
> > DR.
>
> I've managed to solve the problem - it wasn't in the admin.py - it was with
> my models.py.
>
> * stuff*
> *
> *
> changed to:
>
> *class Entry(models.Model):*
> * stuff*
> *
> *
Reply all
Reply to author
Forward
0 new messages