#18948: setting DEBUG to False change behavior of i18n ----------------------------------+-------------------------------------- Reporter: lanyjie | Owner: nobody Type: Bug | Status: new Component: Translations | Version: 1.4 Severity: Normal | Resolution: Keywords: i18n integration | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 ----------------------------------+-------------------------------------- Changes (by claudep):
* needs_better_patch: => 0 * needs_tests: => 0 * needs_docs: => 0 Comment: The problem here is that you probably have no 404.html in your template folder, hence the code path is generating a server error (500) when DEBUG is False. You could probably have seen an appropriate message in your server's logs. This leads me to wonder why we don't have a default 404 content when there is no 404 template. Is this design decision documented somewhere? -- Ticket URL: <https://code.djangoproject.com/ticket/18948#comment:1> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.