#34515: Translatable URL patterns raise 404 for non-English default language
when
prefix_default_language=False is used.
-------------------------------------+-------------------------------------
Reporter: ab | Owner: Sarah
| Boyce
Type: Bug | Status: assigned
Component: | Version: 4.2
Internationalization |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
internationalization, i18n, |
prefix_default_language |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Sanders):
>I agree it still globally works that way, nevertheless, in the case I
describe, when django looks for the language prefix in the requested URL
and there is not language prefix, I would expect django to return "fr",
not to go to the next steps of the algorithm. Because I want
prefix_default_language = False to take precedence on cookies or headers.
Does it make sense?
My 2¢: Is ignoring the process for determining the language the least
surprising choice here though? It all depends on whether no-prefix URL
should refer to a user setting or the site's default language. I mean imho
navigating to a URL I might expect it to show the language in what I chose
🤷♂️
--
Ticket URL: <https://code.djangoproject.com/ticket/34515#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187bc47561f-90619a37-ed74-4ea1-865c-279ffcb7e781-000000%40eu-central-1.amazonses.com.
