I18n URL patterns regardless of I18n setting
See original GitHub issueI’ve just setup a project with 1.0.0rc1 & opted for I18n to be disabled, but the URLs get generated with i18n patterns, resulting in a 404 after I’ve logged in as it loads /en/
for example.
Looks like the app needs two versions of urls.py
for the two outcomes of the i18n setting. This looks like a simple change in copy_files()
so I might fork the repo & try to resolve this.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
django i18n url setting - python - Stack Overflow
I use django to make 2 languages for a website. The url is http://127.0.0.1:8000 ...
Read more >Rails Internationalization (I18n) API - Ruby on Rails Guides
The I18n library will use English as a default locale, i.e. if a different locale is not set, :en will be used for...
Read more >Configure internationalization (i18n) rewrites | Firebase Hosting
Use internationalization rewrites ("i18n rewrites") to serve different content depending on a user's country or preferred language. Here are some example ...
Read more >chrome.i18n - Chrome Developers
Here's how to change the locale using the UI on Google Chrome for Windows: App icon > Options; Choose the Under the Hood...
Read more >Translation | Django documentation
In most cases, it's best to use translated URLs only within a language code prefixed block of patterns (using i18n_patterns() ), to avoid...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@marksweb checking briefly. you can eventually remove the asserts at the end of the test and add a couple of prints in the tests:
I’ll pull your branch to check myself
Locally they run ok Can you open a pull request anyways? Let’s see what Travis says
The test procedure it’s correct (you can also use tox -epyXY to automate the tests)