RE: Can't use admin with apache

What does your Apache log look like? What, exactly, is the 500?

A common issue when deploying is if your fcgi or wsgi script doesn't have
the correct permissions set, which would cause an error that can't be caught
by Django.

-----Original Message-----
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com]
On Behalf Of Matt Smith
Sent: Monday, July 16, 2012 10:24 PM
To: django-users@googlegroups.com
Subject: Can't use admin with apache

Background: I work on my projects using apache2 on my desktop machine, then
just rsync across to the actual server (also apache2), that way I thought I
could avoid the hassle of having things work with the dev server, but not
with apache. Not so. Today I've discovered that the admin works under the
dev server, but not with my apache setup. I replicated this using a brand
new helloWorld project. I've searched the archives, the docs, the book, also
ordinary web search. Found some people had similar problems and fixed it
with apache Alias directives pointing ADMIN_MEDIA_PREFIX to
DJANGO_SRC/contrib/admin/media but this didn't work for me. I get a 500
internal server error, regardless of DEBUG.

Appreciate any help with this.

--
Matt Smith
http://mattsmith.org.nz

--
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.