On Thu, Nov 20, 2008 at 9:15 AM, Serdar T. <[EMAIL PROTECTED]> wrote:
> > ok. so that fix worked....kind of. > > I now get the properly formatted admin login page when I visit > http://mysite.org/admin/ > > But when I log in, the following 500 Internal Server Error appears: > "I'm sorry, that page is currently unavailable due to a server > misconfiguration." > > That is actually a custom error page I placed in my django project's > template directory. When I clear the cache, cookies and authenticated > sessions, I can hit refresh on the admin URL and once again call up > the admin login page (complete with the stylesheets etc.). But then I > get an error stating that cookies appear to not be enabled. And when I > click login, I'm right back where I started: 500 error. > > Any ideas on how to proceed? > Since you don't appear to be in production mode, set DEBUG=True in your settings file so that you get a debug page instead of the bare 500.html rendering. For production, you'll want to set up ADMINS, EMAIL_HOST, EMAIL_HOST_USER, etc. in settings.py so that tracebacks from uncaught exceptions (what's likely causing your 500) get mailed to you. You don't want to expose that information to end users, but you do need it in order to track down what's going on without having to make wild guesses in the presence of no information. Karen --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
