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 mirror of
> > what is on my dev server. My models shows up on the dev's admin screen,
> > just not on the production site... so I doubt that it's something as
> > simple as a botched import.
>
> Ok; time to push this into debug mode. 'Scuse the stupid questions, I
> just need to eliminate the obvious :-)
>
> 1) Are both your servers updated to r3201?

Yes.

> 2) How are you deploying your dev and production servers (e.g., are
> they both apache, or is it apache for production, and django devserver
> for development)

They're both Apache with FastCGI, and mySQL

>
> Assuming your 'missing' model Foo is in an app called 'myproject.myapp'
> 3) Is myproject.myapp in INSTALLED_APPS on both servers?

Yes.

> 4) Are both servers fully syncdb'd?

Yes.

> 5) Does the database on the production server agree that the app has
> been installed?

Yes.

> 6) If you run ./manage.py shell, then run:
> >>> from myproject.myapp.models import Foo
> >>> f = Foo()
> >>> f.save()
> do you get the same behaviour on both servers?

Yes.

> 7) Are there any differences in the PYTHONPATH for the two machines?

No.

> 
> Russ Magee %-)


--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to