On Feb 26, 9:46 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > I've close #760 and #3335 with this comment:
Design decision: Django won't include default 404 and 500 templates. OK. But does that invalidate those bugs? The default templates were a possible solution to fix both of them. Both of these bite the end user when they migrate from development to production so these seem especially ugly to me... changing DEBUG shouldn't break your site. Perhaps under DEBUG=True Django should detect the existence of 404.html or 500.html when one of these errors occurs? Or maybe ./manage.py validate should perform this check? If anything, flatpages docs should mention to the user to make sure they have a 404.html template or it will break when DEBUG=False. That's certainly something I could provide a patch for. Is there another place to add docs that all projects must contain 404.html and 500.html templates? Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
