Aral Roca Gomez
Aral Roca Gomez
Thanks for the clarification @StLyn4
I think is related to https://github.com/aralroca/next-translate/issues/1166
Thanks to report it @bluelakee02. Looks weird, is rendering the `children` before the provider. Plugin code: https://github.com/aralroca/next-translate-plugin/blob/3d6a5044a65769013401fb021883304611842b55/src/templateAppDir.ts#L129 Logs:
This `templateRCCPage` is only executed on **client** pages (RCCPage = React Client Component Page), but it's not the case because your layout is RSCPage.
@brunoscopelliti I replaced this file: ```ts import getT from "next-translate/getT"; const Page404 = async ({ searchParams }: any) => { const t = await getT(searchParams?.lang as string, ["common"]); return (...
> @aralroca Thank you for your advices. Ok, that works, but how I am supposed to render any other language than the default one? It's using the language of the...
Can you try it with the latest version? There are some improvements in 2.3. Thanks
This can happen if you have `app` folder with `pages` folder. If you remove the `pages` folder should work. However we can change this logic inside the plugin to take...
Can you try changing the name of `pages` to another one for a moment, only to verify that is for this?
Try next-translate-plugin prerelease [2.3.0-canary.1](https://github.com/aralroca/next-translate-plugin/releases/tag/2.3.0-canary.1)