[DECLINED] Localized dropdown string is not available

I have…

  • [ ] Checked the logs and have provided uploaded a log file and provided a link because I found something suspicious there.

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

If you create a localized string field, and you want to select value in dropdown selector.
You cannot use the localization.
There is only one dropbox setup in schema, and same in content edition.

Expected behavior

For doing simple, x ordonate fields should be available for fill x dropdowns that depend of localization
In content edit, you can use one dropdown, and each localized value are fill with the good value from the correspondante field filled in the schema.

Minimal reproduction of the problem

Create string field
check localized
Save and edit field
In Editing tab
Editor = Dropdown
only one field for setup values in dropdowns for all locales


  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version

Version: [VERSION]


  • [x] NA
  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge


You want to define allowed values per language? If the answer is Yes, then it is not a bug but a feature request. But it is hard to understand.

Sorry for my uggly english… LOL
Yes I would like to allowed differentes values by language.
If it is a new feature, what mean localization and dropdown input ?

Then you are better with a reference I guess. e.g. lets assume you want to select a country.


  1. Create a new schema called country and give it a localizable name field.
  2. Add a reference field to your other schema.
  3. Select dropdown for this field.

I understood, good idea. Thanks

1 Like