Using localizer about laravel-localized-routes HOT 4 CLOSED

Thank you for your replies.

I did a step-by-step setup and realized I was not up-to-date, so I reinstall and setup everything, including the new FallbackController I did not call using laravel-localized-routes 2.4 and it seems to work…

Thank you so much for your support, and for your awesome and very convenient packages 👍🏻

from laravel-localized-routes.

Hello,

If you look at the Localizer config file, you will find a number of detectors and stores in a specific order.
Each corresponds to a very simpel class that does the logic it needs.
The first supported / detected locale should be returned and stored in every store.

In addition, the browser locale detection is handled by the BrowserLocale package which parses the Request::server('HTTP_ACCEPT_LANGUAGE'). Does this have the expected locale?

https://github.com/codezero-be/browser-locale/blob/c8563bdd0fdce0e6edcce3daeda5b2fddb981f83/src/Laravel/BrowserLocaleServiceProvider.php#L28-L32

Also ensure that the 3 ServiceProviders have been discovered and any cached config is up to date.

from laravel-localized-routes.

I just tried the Chrome plugin on a local project using the setup described in this packages Readme, and I did get the correct locale.

I did have to remove the cookies before reload, and also use a route that did not have a locale in the url, like fr/some-route. A locale in the url will always win, followed by session and cookie.

from laravel-localized-routes.

I'm happy to hear that it's working!
Thanks for the thumbs up!

from laravel-localized-routes.