First, make sure it is listed in the installed apps in your settings
file. Then, make sure the Admin() innerclass is defined in the model
(and that is has proper whitespacing etc.)
On 6/23/06, Steven Ametjan <[EMAIL PROTECTED]> wrote:
>
> I'm not quite sure how it happened, but one of my models d
Hi Steven.
this one got me stuck for hours (grin).
if your INSTALLED_APPS is right and your admin inner class too, you
probably have an error on an import on your model class.
fire up the shell on your server setup. can you import your model
module?
--~--~-~--~~~---
On 6/24/06, arthur debert <[EMAIL PROTECTED]> wrote:
> this one got me stuck for hours (grin).
> if your INSTALLED_APPS is right and your admin inner class too, you
> probably have an error on an import on your model class.
FYI - To help avoid this problem in the future, I have just committed
a
Hi Russel.
Thanks for the patch. I am sure this one will save newbies a few hours
of starting blankly at the screen.
cheers
Arthur
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to t
Not sure if this makes a difference or not, but when I run "manage.py
validate" it says that there are 0 errors... and like I said
originally... The files on my production server are an exact mirror of
what is on my dev server. My models shows up on the dev's admin screen,
just not on the producti
On 6/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Not sure if this makes a difference or not, but when I run "manage.py
> validate" it says that there are 0 errors... and like I said
> originally... The files on my production server are an exact mirror of
> what is on my dev server. My
On Sat, 2006-06-24 at 23:57 -0700, [EMAIL PROTECTED] wrote:
> Not sure if this makes a difference or not, but when I run "manage.py
> validate" it says that there are 0 errors... and like I said
> originally... The files on my production server are an exact mirror of
> what is on my dev server. My
Russell Keith-Magee wrote:
> On 6/25/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Not sure if this makes a difference or not, but when I run "manage.py
> > validate" it says that there are 0 errors... and like I said
> > originally... The files on my production server are an exact mir
My guess would be caching or database discrepencies. Have you tried
accessing the production database through the dev server? Also have you
tried to delete .pyc files?
-rob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Ok; here's a few more questions:
1) Update both servers again - has Malcolm's r3202 patch resolved anything?
2) If you run ./manage.py shell, then run:
>>> from django.db import models
>>> print models.get_apps()
>>> print models.get_models()
What do you get (on each server)?
3) Exactly how ha
Malcolm Tredinnick wrote:
> On Sat, 2006-06-24 at 23:57 -0700, [EMAIL PROTECTED] wrote:
> > Not sure if this makes a difference or not, but when I run "manage.py
> > validate" it says that there are 0 errors... and like I said
> > originally... The files on my production server are an exact mirro
Okay what solved my problem was removing imports of my models from
urls.py. I had a few generic view wrappers that were short so I had
just defined them in urls.py for now and that was causing a problem
when django was launched from fastcgi or mod_python but not
django-admin.py runserver.
--~--~
12 matches
Mail list logo
