Repository navigation
Multi-language support / i18n of labels, descriptions and display-values #201
Description
Summary
Currently all my ClientConfig-settings have German labels.
As I'm probably getting international clients soon, I'd need to make it dynamic.
Step to reproduce
On the setting's label I tried using: [[%website.form.name]], %website.form.name and website.form.name.
Observed behavior
I see the string, and not a translated lexicon-value.
Expected behavior
A way for internationalization on the labels and descriptions fields.
Environment
MODX Revolution 2.8.4-pl, ClientConfig 2.3.3-pl
Activity
sebastian-marinescu commentedon Feb 22, 2023
As I wasn't to sure, that my lexicon would be loaded in the ClientConfig-CMP, I also tried:
[[%clientconfig.label]],%clientconfig.labelandclientconfig.label- which also doesn't work.It should be possible on settings and groups.
sebastian-marinescu commentedon Feb 22, 2023
I started a bounty of 50,- $ on this:
https://app.bountysource.com/issues/117206875-multi-language-support-i18n-of-labels-and-descriptions
[-] Multi-language support // i18n of labels and descriptions[/-][+][BOUNTY] Multi-language support // i18n of labels and descriptions[/+]Mark-H commentedon Feb 22, 2023
Should that follow the language of the context (in multi context mode) or of the user?
sebastian-marinescu commentedon Feb 22, 2023
I think it should follow the manager-language that the manager chooses.
There could be an international editorial staff, where one uses the CMS in EN, another one in DE, and another one in CZ.
Each one should feel comfortable using/editing stuff, hence it should be in the manager-user's language.
sebastian-marinescu commentedon Feb 23, 2023
I just noticed, that ideally this would also work for values - consider this:
Normal==normal||Kursiv==italicas options on a selectbox.Would be beautiful, if I could do something like this:
%website.settings.fonts.normal==normal||%website.settings.fonts.italic==italic[-][BOUNTY] Multi-language support // i18n of labels and descriptions[/-][+][BOUNTY] Multi-language support / i18n of labels, descriptions and display-values[/+]sebastian-marinescu commentedon Jul 17, 2025
Slight Off-Topic
I want to push this issue more, so I checked my old bountysource-link and realized that they are gone - and so is my money....
Anyways, does someone here have a fair, working and legitimate alternative to it?
I registered at "gitpay.me", but in the 5 minutes of using/navigating it, the whole app/website crashed twice:
Doesn't seem very trustworty.
Any recommendations?
alexanmtz commentedon Jul 17, 2025
@sebastian-marinescu I'm the Gitpay maintainer, and I understand your frustration with BountySource. I have followed that, and we have Gitpay up for over 5 years, supporting Open Source and many projects throughout these years.
Thank you for reporting the crash; it's now resolved, and you can access it again. Please don't hesitate to contact me if you have any questions or concerns. You can contact me on our Slack or alexandre@gitpay.me
syedbarimanjan commentedon Jul 17, 2025
I can vouch for gitpay, have received bounties from it. A bounty hunter interested in working in this.
axelvyrn commentedon Aug 16, 2025
Hello, is this issue open to work on? I might have a fix to this for a lexicon support to ClientConfig.
samuel-asleep commentedon Jan 20, 2026
@sebastian-marinescu is this issue open to work on 🫠
Mark-H commentedon Jan 20, 2026
Yes this issue is still open with no PR for it, but the bounty may or may not be available anymore.
Karthikramesh12 commentedon Aug 31, 2026
I'm sorry for asking again, but is this issue still open?
[-][BOUNTY] Multi-language support / i18n of labels, descriptions and display-values[/-][+]Multi-language support / i18n of labels, descriptions and display-values[/+]Mark-H commentedon Aug 31, 2026
as you can see, a pr was submitted the other day #221
as bountysource no longer exists, that bounty is gone.
sebastian-marinescu commentedon Sep 1, 2026
@alexanmtz
Wanted to try to add a bounty on your new platform. Doesn't work.
sebastian-marinescu commentedon Sep 1, 2026
@Karthikramesh12 @samuel-asleep @axelvyrn @syedbarimanjan
The issue is still open. My willingness to pay a little bounty for this is still there, but it seems someone created a PR for it:
#221
samuel-asleep commentedon Sep 1, 2026
If #221 doesn't fix it, I can try it and make a submission.
Also about gitpay there is an issue with their stripe at the moment am not to sure the details but it unusable for a while. If I submit a working fix, would it be fine to handle the bounty through GitHub Sponsors instead?
alexanmtz commentedon Sep 1, 2026
@sebastian-marinescu thanks for reporting. It’s fixed now. You can try it again.
@samuel-asleep we are back 🥹🙌
moyuziya commentedon Sep 9, 2026
Hello @sebastian-marinescu and @alexanmtz — I noticed Gitpay task 1224 references this issue, and #221 already proposes a substantial implementation. Before preparing any competing or supplementary work, could you confirm whether a cash bounty is currently funded, the amount and payment route, and whether there is any remaining scope available for assignment (for example the MODX integration verification mentioned in #221)? I would only proceed after scope and acceptance criteria are agreed. Thank you.
Mark-H commentedon Sep 9, 2026
Getting real tired of this.