I assume the dropdown will be displayed on the frontend, and depending on which language the user has selected the text in the dropdown will change, yet the values will always be the same? That also means in the Umbraco backend you will always have 'red', 'green' and 'blue' as selectors and not different values depending on which language the backend is using?
In that case you could just use resource files for the different language texts (some info here) or you could possible use the build-in dictionary for that as well, both probably in a custom .Net control.
no actually it's for the backend. Hm, I need to be more precise in my questions. I guess I even messed up my subject... Should be "dropdown with custom values and translateable display texts" or something, just as in my html sample.
For example a documenttype where the editor are supposed to select one of three options (for example colors).
We have dropdown with or without publishing keys as a built in datatype. But when publishing keys the values = some node id's with no actual meaning, or not publishing keys means values = displayed text (which I like to be able to change or even translate automatically).
I really like the values to be understandable, like "red", "green", "blue".
Dropdown with custom keys and translated values?
Hi,
I need a dropdown with custom key names, and translated value names, is that possible with built in datatype or some package?
Like so:
<select name="selectcolor">
<option value="red">Röd</option>
<option value="green">Grön</option>
<option value="blue">Blå</option>
</select>
then I could easily handle the datatype with understandable key names, and be able to copy it to another instance without problem.
If there is one with only the custom keys, that is also good.
Kind regards
Jonas
The site is a 4.0x one.
Hi Jonas,
I assume the dropdown will be displayed on the frontend, and depending on which language the user has selected the text in the dropdown will change, yet the values will always be the same? That also means in the Umbraco backend you will always have 'red', 'green' and 'blue' as selectors and not different values depending on which language the backend is using?
In that case you could just use resource files for the different language texts (some info here) or you could possible use the build-in dictionary for that as well, both probably in a custom .Net control.
Hope that helps,
Sascha
Hi Sascha,
no actually it's for the backend. Hm, I need to be more precise in my questions. I guess I even messed up my subject... Should be "dropdown with custom values and translateable display texts" or something, just as in my html sample.
For example a documenttype where the editor are supposed to select one of three options (for example colors).
We have dropdown with or without publishing keys as a built in datatype. But when publishing keys the values = some node id's with no actual meaning, or not publishing keys means values = displayed text (which I like to be able to change or even translate automatically).
I really like the values to be understandable, like "red", "green", "blue".
Regards
Jonas
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.