Ashkan
I am trying to use ex_cldr for localization. I want to use path parameters to change languages and it doesn’t work, but works with query parameters. Requesting http://localhost:4000/en will use fa as locale but http://localhost:4000/?locale=en uses en.
I have added this to the endpoint.ex:
plug Cldr.Plug.SetLocale,
apps: [:cldr, :gettext],
from: [:path, :query],
gettext: MyAppWeb.Gettext,
cldr: MyApp.Cldr
This is the cldr module:
defmodule MyApp.Cldr do
use Cldr,
locales: ["en", "fa"],
default_locale: "fa",
gettext: MyAppWeb.Gettext
end
And my routes:
scope "/:locale" do
pipe_through [:browser, :simple_layout]
pow_routes()
end
scope "/:locale", MyAppWeb do
pipe_through :browser
get "/", PageController, :index
end
scope "/:locale/admin", MyAppWeb do
pipe_through [:browser, :protected, :admin_layout]
end
scope "/" do
pipe_through [:browser, :simple_layout]
pow_routes()
end
scope "/", MyAppWeb do
pipe_through :browser
get "/", PageController, :index
end
scope "/admin", MyAppWeb do
pipe_through [:browser, :protected, :admin_layout]
end
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kip
@ashkan, I’m the author - I’ll take a look and see if there’s an issue. Feel free to open an issue at https://github.com/elixir-cldr/cldr/issues
Can you confirm that you are using Phoenix version >= 1.3?
path_paramswas added then and its what the plug uses for locale detection in paths.Ashkan
I am using phoenix 1.5.
I am not sure If I understand correctly but phoenix is able to detect the parameter, this is what I saw in server logs
Parameters: %{"locale" => "en"}when I requesthttp://localhost:4000/enandpath_params: %{"locale" => "en"}is inconn. I havefrom: [:path, :query]inSetLocaleplug. Allex_cldrvariables inconnare set to usefa. I don’t know how to further investigate that.kip
Wold you kindly check that you have
Cldr.Plug.SetLocaleconfigured afterplug :matchin your endpoint?plug :matchis what populates thepath_paramsand therefore its importantPlug.Cldr.SetLocalecomes after that.LostKobrakai
There’s no explicit
plug :matchin phoenix.Ashkan
There is no
plug :matchin my endpointkip
Ahhhhhh. OK, in the case I’m looking for help too
Is there a way to have a user plug run after
plug :matchand beforeplug :dispatchor Phoenix equivalents?kip
Clearly demonstrating my lack of Phoenix knowledge. But it looks like you would need to put
Cldr.Plug.SetLocalein your pipeline, not the endpoint. Possible you can try that? As best I can tell from the docs, the pipeline is not run unless a route is found - and I believe when a route is found thatpath_paramsis decoded.So, for example:
LostKobrakai
That’s true. Pipelines are run after a route is matched, as the matched route determines which pipelines need to run.
Ashkan
Thanks that worked.
P.S.
You were right
path_paramswas empty at that point in endpoint. I used another plug to test that. Previously I have check it near the end of processing pipeline.