Panel: Translations of section labels not working

Kirby 3 Solved ✅
1

I am totally stuck: I have created a bilingual blueprint with sections, langauge switching in the panel doesn´t work at all here:

pages/termine.yml

title:
  de: Termine
  fr: Dates

sections:

  draft_events:
    label:
      de: Entwürfe
      fr: Dates non publiées
    extends: sections/termine
    status: draft

  published_events:
    label:
      de: Veröffentlichte Termine
      fr: Dates publiées
    extends: sections/termine
    status: listed

sections/termine.yml

type: pages
parent: site.find("termine")
sortBy: eventStartDate desc
templates: termin
empty:
  de: Noch keine Termine
  fr: Pas encore de dates
layout: table
columns:
  eventStartDate:
    label:
      de: Startdatum
      fr: Date de début
    value: "{{ page.eventStartDate.toDate('d.m.Y') }}"
  eventHost: true
  eventHostArea: true

When I change the language in the panel from German to French, neither the section labels nor the table titles are displayed in French. They are still displayed in German.

The language settings of the site are o.k. All other blueprints (without sections) work as expected.

Any hints very welcome.

TIA

Thomas

2

Seems to work fine for me.

Screenshot 2023-03-31 at 13.03.14
Screenshot 2023-03-31 at 13.03.14904×456 31.7 KB

Screenshot 2023-03-31 at 13.02.46
Screenshot 2023-03-31 at 13.02.46924×380 29.1 KB

3

Thanks for testing, Sonja. Here no chance at all:

de
de1128×829 33.4 KB

fr
fr1128×829 34.5 KB

The blueprint headline (Termine/Dates) seems to come from the content files. Are there any other factors, that influence, what is shown in the panel. Any caches to clear? Any config to reset? Just updated to 3.9.3. No effect.

4

What you see there is not the blueprint headline but the page title, so this is a misunderstanding, this is content, not UI.

The translated blueprint title is shown when you select a template.

And the section label “Entwürfe” is shown correctly in German. Note that these labels depend on the chosen User language, not the selected translation language. So in line with the rest of the UI and as intended.

5

Thank you so much, Sonja. Just found an old post from 2015 from you. Same problem, same solution then. I really confused content and user language. Sorry for bothering you with this issue.

6

No worries!