What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello, guys! I got a little bit stuck on a matter of routes and translations, with multistores. The

U0180L85PNH
U0180L85PNH Posts: 2 🧑🏻‍🚀 - Cadet
in Help

Hello, guys! I got a little bit stuck on a matter of routes and translations, with multistores.

The shop context is as follows: there is only one domain [www.domain.com](http://www.domain.com) , and the different shops can be accessed by adding the store identifier, for example /de-store for the DE shop.

Concrete example: on homepage, the route is defined as /{root}_,_ where root accepts nothing or allowedLocales. The url for homepage should, in the end, look like [www.domain.com/de-store/nl](http://www.domain.com/de-store/nl). The prefix /de-store of the routes is added in YvesBootstrap, where the mounting of controller providers takes place.

If I access the hompage url with the newly selected language, nothing happens – no errors, still landing on homepage in the browser, but no translations for the new language (NL) are applied.

Does anyone ever encountered something simillar or maybe has an idea of where should I look next?

Thank you!

Comments

Categories