#31540: i18n URLs are not matched against the fallback language.
--------------------------------------+------------------------------------
Reporter: osxisl | Owner: nobody
Type: Bug | Status: new
Component: Internationalization | Version: 3.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by osxisl):
Replying to [comment:7 Carlton Gibson]:
> If `id-button` **correctly** falls back to `id` as the langauge code,
but then tries to match the URL against `id/` — which it doesn't match.
Are you sure, that a fallback from `id-button` to `id` as the language
code is a correct behaviour when we have set
**prefix_default_language=False** ?
I think, it may be a some kind of correct behaviour in case we set
**prefix_default_language=True**, but when we hide default language, we
get a big problem - we need to check that we don't have items in DB with
slug that begins with any of our "language code" + "-" +"any word".
For me it looks like the principle of encapsulation is broken.
For example: When website editor adds content to English version of a
website he don't need to have a limitations, to set a slug `id-button` or
`in-love` if the website doesn't have a language `id-button` or `in-love`
even if it has "id" and "in" language.
--
Ticket URL: <https://code.djangoproject.com/ticket/31540#comment:8>
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/064.7af1b21ac8b4e27d7f59ce3eab3669bf%40djangoproject.com.
