Re: [Django] #18948: setting DEBUG to False change behavior of i18n

[Django]

#18948: setting DEBUG to False change behavior of i18n
--+--
 Reporter:  lanyjie   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  Version:  1.4
 Severity:  Normal|   Resolution:  worksforme
 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 lanyjie):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 @claudep: indeed, after providing 404.html everything worked just fine.
 Thanks!

-- 
Ticket URL: 
Django 
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.

Re: [Django] #18948: setting DEBUG to False change behavior of i18n

[Django]

#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
--+--

Comment (by aaugustin):

 Providing a default 404 content is tracked in #18807.

-- 
Ticket URL: 
Django 
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.

Re: [Django] #18948: setting DEBUG to False change behavior of i18n

[Django]

#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: 
Django 
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.

[Django] #18948: setting DEBUG to False change behavior of i18n

[Django]

#18948: setting DEBUG to False change behavior of i18n
--+--
 Reporter:  lanyjie   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  1.4
 Severity:  Normal|   Keywords:  i18n integration
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 I pretty much followed the i18n tutorial setup:
 {{{
 urlpatterns += i18n_patterns('', url(r'', include(my_urls))
 }}}
 and when settings.DEBUG = True, if visit
 {{{
 http://my.web.site/
 }}}
 the server will first send out a http/1.1 302 response, then the browser
 would immediately send a new request of something like:
 {{{
 http://my.web.site/en/
 }}}
 depending on the default language of the browser, which is the expected
 behavior. But when I set DEBUG=False, the server would then directly send
 out a 500 response, which seems just wrong.

-- 
Ticket URL: 
Django 
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.