@Paul_Brats Any updates about using slugs and internationalization?
I can’t manage to have the same collection in several languages with the same slug. What I’m trying to achieve is allowing to change the website’s language and keep the same page open but in another language.
I believe the slug will be translated to the selected language being used. So not sure how to go about keeping the slug the same.
Without GraphQL how to create a slug system?
Hello there @mauriciabad I wrote the following article explaning how to achive this behavior on dynamic pages with dynamic slugs in a Next.js project: Learn How to Internationalize Dynamic Routes Using Strapi and Next.js.
But if you want to use the same “slug” for different locales, you probably won’t be able to use the UUID field of Strapi, instead you can try using a text field, and then filter the record specifying the locale that user selected in your website.
Great article. Quick question are you part of the Strapi “write for the community” it’s a great way to share cool things about Strapi and get paid. We are always looking for more intermediate to advanced topics published by folks that love Srapi.
I see you used GraphQl, nice, I am going to try to recreate your example using REST.
I’m experiencing this exact same issue. Were you ever able to solve it?
as far as I remember: unfortunately no ![]()