I ran into exatly the same issue just now (10 years after your post). When I use compress in production with DEBUG=False, I get a 500 error. I wish I had read your post 5 hours ago... Everything works fine now.
-- Eki On Monday, 25 January 2010 23:05:57 UTC+2, Damon Jablons wrote: > > I do have a 400 and 500 error page. > > I've been mulling over this issue for a couple days and I just > discovered what it was. I was using the css/js compression app called > "compress" which only runs if DEBUG=True. It was throwing some error, > so I removed it and things work fine now. > > In the immortal words of Homer Simpson, "Do'h!" > > On Jan 25, 3:40 pm, Ted Nyman <tnm...@gmail.com> wrote: > > Have you created a 404.html and 500.html in your template directory? > > > > On Mon, Jan 25, 2010 at 12:37 PM, Damon Jablons <damonjabl...@gmail.com > >wrote: > > > > > I work on my django site locally, and pull from the repository > > > remotely. On my local machine, I have DEBUG = True, and on my remote > > > machine I have DEBUG = False. Whenever I set the server's DEBUG to > > > False, the server presents a 500 error, and there's nothing to be > > > found in the Apache logs. If I set DEBUG to True, the site runs > > > perfectly fine. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6daa2f56-7225-44c3-897a-37397695cf0a%40googlegroups.com.
