Ruslan Zainetdinov
Ruslan Zainetdinov
This option could be useful.
Yes. And I also use next-i18next for i18n. Here is both configs. next.config.js: ``` /** @type {import('next').NextConfig} */ const withPlugins = require("next-compose-plugins"); const { i18n } = require("./next-i18next.config"); const withPWA...
I will try to reproduce this issue on clean next/drupal setup with the same language configuration.
@shadcn I used [node:title] and tried [node:source:title]. I think in this case it doesn't matter. I made an example with 2 nodes: - **1 product** which is **translated** node with...
Yes. In this example above. In general some nodes can have translations, but some can exist only in one language. I think it's not specific to a particular case, but...
Filtering in params for getPathsFromContext can't solve the problem because any filtered resources will be mapped through all the nextjs locales anyway.
Sorry for the mess. There should be only last commit #181 [12c412e](https://github.com/chapter-three/next-drupal/pull/181/commits/12c412e309c744cc0b9dc4d800c8b7f0292cc887)
The reason is that Drupal will search through redirects for path with prefix of original locale, but nextjs sending path without locale prefix for default locale so no redirects are...
@shadcn yes, this is relevant for DrupalClient too.
Merged this with the new file structure (with Guides)