You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a project in which I enabled the localization feature Payload provides, and it seems to work just fine on text fields. I can set the locale to * when calling payload.create and then I can set all the languages at once by providing an object like:
{"en": "a", "es": "b"}
However this same logic seems to fail when it comes to upload type fields, complaining that the field is invalid. From reading the documentation and experimenting via the UI it's clearly supported to localize upload fields so I'm wondering if it uses another way, if it's a bug or if it's simply not supported? I assume it may have to do with the fact that it's a relationship field.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a project in which I enabled the localization feature Payload provides, and it seems to work just fine on text fields. I can set the locale to * when calling payload.create and then I can set all the languages at once by providing an object like:
{"en": "a", "es": "b"}
However this same logic seems to fail when it comes to upload type fields, complaining that the field is invalid. From reading the documentation and experimenting via the UI it's clearly supported to localize upload fields so I'm wondering if it uses another way, if it's a bug or if it's simply not supported? I assume it may have to do with the fact that it's a relationship field.
Beta Was this translation helpful? Give feedback.
All reactions