I’m creating a multilanguage site (my first kirby site btw) and it works quite well, but the translated “options” from my blueprint do not get translated on the website itself. My blueprint looks like this options: monday: en: monday fr: lundi tuesday: en: tuesday fr: mardi I…

For the first option, you would define the variables in your language files: return [ 'code' => 'fr', 'default' => false, 'direction' => 'ltr', 'locale' => 'fr_Fr', 'name' => 'Français', 'translations' => [ 'monday' => 'lundi', 'tuesday' => 'ma…

Hey @luap , Welcome to the Kirby forum. [image] luap: but the translated “options” from my blueprint do not get translated on the website itself. The translated labels are only displayed in the Panel, they are not stored in your content files (only the value is, in this case monday and tuesd…

Hey @texnixe , thanks for the quick reply before the weekend! I am not only new to kirby but also to php, to be honest. Your first proposal looks good, translating seven “days” is no problem. But I couldn’t figure out where to put my “day” variable there (for the seven days of the week…). My guess …

Thank you! That worked! I had missed the ->value before. But I still had to “translate” the days in my english default language file.

Yes, you have to do that for every language. Sorry for being unclear.

No Problem, since you mentioned it in another question I had read before.

Show translated blueprint options on final site?

The CMS Questions

Topic		Replies	Views
Mutlilanguage fields not getting translation Questions v2	5	596	June 7, 2018
Multi language troubles Questions v3	8	919	November 11, 2021
Translating blueprints Questions v3	4	762	July 8, 2021
Translate panel fields doesn't work Questions v2	7	1993	May 4, 2015
Multilanguage options Questions v3	4	238	July 11, 2023

Show translated blueprint options on final site?

Related topics