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
The localized collection field (Description) that you are working with has no connection to Lokalize as far as I know. Lokalize is a system to create localized strings. We use it to translate elements in our frontend application written in React.
Thanks, I already realized that I wrongly connected those two. I currently have a small system of mine for the non-dynamic content of the front-end (which doesn't involve cockpit) but I might switch to this dynamic (through CMS UI user translation). However, I understood how to use the Localize switch in order to have definitions of collection/singleton field values in multiple languages. This link helped me: https://getcockpit.com/documentation/reference/configuration
I would appreciate a minimal clear example of how to use the Localized option in a collection's text field.
Right now, when I set a field's Localization switch to ON, I then can't select a key from the Lokalize Project although I have some keys added.
PS. Hello and thanks for the amazing content!
The text was updated successfully, but these errors were encountered: