The locale doesn't change for pages other than index page
See original GitHub issueI tried using next-translate v1.0.7 Using the sub path /ja
it works for index page localhost:3000/ja
, but not working when navigating to other page, it keeps returning to default en locale localhost:3000/ja/product/detail
ready - started server on http://localhost:3000
next-translate - compiled page: /product/detail - locale: en - namespaces: common - used loader: getInitialProps
next-translate - compiled page: / - locale: ja - namespaces: common - used loader: getStaticProps
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:11 (2 by maintainers)
Top Results From Across the Web
The locale doesn't change for pages other than index page #619
I tried using next-translate v1.0.7 Using the sub path /ja it works for index page localhost:3000/ja, but not working when navigating to ...
Read more >Why won't my CSS work on other pages besides the index?
On my index page, the CSS works, but whenever I preview the different path pages, it doesn't appear. Weird thing is, I literally...
Read more >Localized Versions of your Pages | Google Search Central
Tell Google about localized versions of your page. Stay organized with collections Save and categorize content based on your preferences. If ...
Read more >How to Change your Default Index Page in the htaccess file
The workaround to this is just to set the WP “site URL” to https://domain.com/index.php in general settings. Then set it back to just...
Read more >Create multilingual SharePoint sites, pages, and news
In the site information panel, remove or edit content that has an incorrect translation. If it is empty, users of that language will...
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 Free
Top 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
This still seems to be an issue in v12.1.4
You need to update to the last version of Next.js. Should be fixed after this PR https://github.com/vercel/next.js/pull/21930.
Try Next.js 10.2.3 😊