Translations in shared layouts don't work anymore in 1.4.0
See original GitHub issuehttps://github.com/vinissimus/next-translate/pull/743 introduces the same bug reported here already: https://github.com/vinissimus/next-translate/issues/604
- also the author of https://github.com/vinissimus/next-translate/pull/743 already mentioned that the change back then was reverted because of https://github.com/vinissimus/next-translate/issues/604 and now the change in 1.4.0 is introducing the issue again
- we experience the same issue
steps to reproduce:
- use repo https://github.com/vinissimus/next-translate/issues/604
- use latest 1.4.0 next-translate version in package.json
- install dependency
- start the project with
yarn devand click on the links
Issue Analytics
- State:
- Created a year ago
- Comments:22 (17 by maintainers)
Top Results From Across the Web
Translations in shared layouts don't work anymore in 1.4.0 #834
steps to reproduce: use repo Translations in shared layouts don't work in 1.0.6, while they work in 1.0.
Read more >django internationalization and translations issue
Problem 2 - I have created my own locale file with django-admin.py makemessages -l et, added the translation string into file, but they...
Read more >How to enable translated email layouts/templates t...
I've been using static translation for the notifications and already done ... the layout/template translation functionality doesn't work.
Read more >Translations (Symfony Docs)
When you work with many translation messages in different languages, it can be hard to keep track which translations are missing and which...
Read more >Compose Foundation - Android Developers
androidx.compose.foundation:foundation:1.4.0-alpha03 and ... b/229378536); Introduce experimental APIs to share item provider logic between Lazy layouts.
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

great news, thanks! who needs to add the tests? I havent really understood what the cases are… maybe we can also revert first with this PR https://github.com/vinissimus/next-translate/pull/836 and someone else delivers additional tests afterwards?
Same here with 1.6.0, is there any workaround ?