Translate:false and structure field

Kirby 2 Solved ✅
, ,
1

Hi guys,

So today I ran into an “issue” and I want to check with you guys if it is a normal behavior. Let me explain: I have a website with 3 languages (EN-default, FR, CN) and some of my fields are not meant to be translated in order to ease the maintenance and avoid mishandling.

Everything in my setup works fine expect for Structure fields like this one :

press_materials:
    label: Press materials
    type: structure
    fields:
      label:
        label: Label
        type: text
      attachment:
        label: Attachment
        type: select
        translate: false
        options: query
        query:
          fetch: files
          value: '{{filename}}'
          text: '{{filename}}'

When I add an entry in EN-default only, I can use it on the front side without any issue and data.en.txt looks like this:

- 
  label: Logo PNG
  attachment: LOGO_4MOD_PNG.zip
- 
  label: Logo SVG
  attachment: LOGO_4MOD_SVG.zip
- 
  label: Worldwide divisions SVG
  attachment: LOGO_4MOD_WORLDWIDE.zip

As soon as I translate an entry (only the Label, as the Attachment is set to translate:false, remember) I got an error: The attachment field becomes empty in the panel and data.fr.txt looks like this:

- 
  label: Logo PNG
  attachment: null
- 
  label: Logo SVG
  attachment: null
- 
  label: Worldwide divisions SVG
  attachment: null

Is this a known structure field / translate:false combination issue or am I doing something wrong ?

Thanks in advance for your feedback !

2

Afaik a structure "sub"field is language agnostic, as “the” field that is seen by kirby i18n is the structure field itself.

3

The problem is that the entries in each language have no counterpart in another language. In fact, you can delete entries from one language without automatically deleting them from the other language. Also, these entries can have different sort orders in different languages. Without adding a unique ID of some sort, it is completely impossible to match these entries across languages. Therefore, the translate: false option on a per field basis within the structure field currently does not make sense.

4

Thanks guys for your answers, I was pretty sure it was normal.

I’ll find a way to achieve this in a different way