recently I was trying to configure the custom header links to allow it shows up according to the specific language (locale) and realized this feature is not working as expected for some of the languages such as zh_CN and en_BG… seems whichever with “_” in the middle of the string is not working but for “fr” “ca” “en”… are working smoothly. what I have already tried. firstly set forum locale to “en” then set custom header link locale to zh_CN i logged in with an another regular user set interface language to zh_CN then the header won’t showing up . then I have also tried to set forum locale to “en” then set custom header link locale “ca” logged in with another regular user set interface language to “ca” as well then it shows the header . which tells me the zh_CN is not working as expected really appreciate if someone can help me with this issue to make zh_CN language works as expected thanks a head

a dash should work, zh-CN, that’s the web format no way for you to have known of course, so we should correct this — once this update lands either - or _ will work https://github.com/discourse/discourse-custom-header-links/pull/86

is there any possible to make multiple language points to one locale string settigns? for example locale: “en-US, en-UK” since for me most of the cases should be the same therefore if possible to make it as one line configuration would be much better then use two exactly the same objects for only update the en-US to en-UK

It’s not currently possible, but should be doable. I can give it a try when I have some time (or someone else can feel free to make a pull request!)

[image] Michael_Liu: for example locale: “en-US, en-UK” Wouldn’t just en do the job?

not really the en present for en-US and en-GB present for en-UK you can give a try [The image shows a file directory with folders containing ".yml" files for translations, and an arrow pointing to a highlighted folder named "sv.yml." (Captioned by AI)] you can give a try but yeah that’s not a big deal as long as I know the right way to reference the proper file which is “-” instead of “_” is good enough.

Custom header link locale is not working for some languages

Product Support

Jagster (Jakke Flemming) May 16, 2025, 9:30pm 6

Wouldn’t just en do the job?

Topic		Replies	Views
Missing Custom Header Links after update Bug custom-header-links	4	713	April 24, 2023
Cannot get the Custom Header Links to display? Product Support custom-header-links	15	1093	September 3, 2023
Making a theme translation for Custom Header Links Development custom-header-links	5	457	May 19, 2020
Pull request adding locale attributes to links Feature completed , custom-header-links	0	194	April 21, 2023
Custom Header Links Theme component official , custom-header-links	69	54828	June 6, 2026

Custom header link locale is not working for some languages

Related topics