The discussion centers around the “Header Locale Selector” theme component by Ahmed_Gagan, which adds a language dropdown to the site header for multilingual users. Users praise its utility, with Heliosurge calling it “amazing” and suggesting mobile responsiveness and flag alternatives like country codes. khenmu recommends making it more prominent with flags. Some users report issues: volanar claims it doesn’t work, but Arkshine clarifies it was never broken — a misunderstanding with another component — and confirms it works on the latest Discourse version. A PR was merged to fix minor issues Arkshine. fahmi_fareed shares code to restrict locales (e.g., only ‘en’, ‘ar’) and optimize performance, which Arkshine affirms requires using available_locales in the theme’s settings. Later, joshhabka reports a new issue, while nat notes Discourse’s built-in content localization may render this component redundant. The component remains tagged as broken despite working, due to initial confusion.
This theme component adds an available language drop-down to the site header. It will be very helpful for the user’s who are not familiar with the default site language.
Note: This feature is only available for logged-in users.
This is an amazing fantastic feature! It is my recommendation the Team should consider adding this component minimally as a pre installed theme-component in core!
If I enable the chat plugin it is going to be very crowded. Perhaps even have it configurable to use flags on Desktop with mobile using the 2 letters similar to wasvit earlier windows? Been Awhile. lol
Though scaling might work to be similar on size as the search mag glass
To begin with, the component was never broken!
There was a misunderstanding about another Discourse theme component that Volanar reported as broken.
I tested the component, which still works on the latest Discourse version.
However, it still requires some updates to modernize it, resolve a deprecation, and fix minor issues so it will work well on the latest Discourse version.