Translated options in multilingual panel in separate language file

Kirby 3
1

Hello,

I have a multilingual panel and I save my translation values in a separate file.
It works as expected and I can use the values in my blueprint.

Working example:

label: my.translation.value

Mutlilingual values in options are working in general, see example:

label: my.translation.value
type: select
options:
   option1:
      en: 'bli'
      de: 'bla'
      fr: 'blubb'
   option2:
      en: 'bli'
      de: 'bla'
      fr: 'blubb'

However, it does not work or it least I don’t know how for type:select options, when values are stored in a separate language file.

label: my.translation.value
type: select
options:
   option1: my.translation.option1
   option2: my.translation.option2

Any hints, how to solve this?
Thanks for answers in advance :slight_smile:

2

This is known issue as

3

Thank you for your answer.
So I’ll wait for a fix :slight_smile:

4

If you need a workaround until this is fixed, you can define the field programmatically, similar to the approach here, only using the user language instead of the currently selected language:

5

Thank you Sonja. I think for the moment it’s ok to translate the values inline, instead of a separate file and wait until the issue is implemented.