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
{{ message }}
This repository has been archived by the owner on Jan 4, 2021. It is now read-only.
I think it would be kind of helpful if we could globally set something like a “translate: false” on a blueprint instead of every single field inside it.
In this case Kirby could automatically switch the user to the default language if he tries to edit the affected page and disable the option to switch to the alternate language.
Use cases are for example some kind of internal settings blueprints / pages which shouldn’t be translatable. In case that the frontend editor is on an other language than the default, he wouldn’t need to manually switch the language back to default because of all the greyed out, disabled fields and it reduces the possibility that a developer forgets to disable a new field inside the blueprint.
Nice to have (but not necessary):
Ability to disable the translation globally but then enable translation for specific single fields.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think it would be kind of helpful if we could globally set something like a “translate: false” on a blueprint instead of every single field inside it.
In this case Kirby could automatically switch the user to the default language if he tries to edit the affected page and disable the option to switch to the alternate language.
Use cases are for example some kind of internal settings blueprints / pages which shouldn’t be translatable. In case that the frontend editor is on an other language than the default, he wouldn’t need to manually switch the language back to default because of all the greyed out, disabled fields and it reduces the possibility that a developer forgets to disable a new field inside the blueprint.
Nice to have (but not necessary):
Ability to disable the translation globally but then enable translation for specific single fields.
The text was updated successfully, but these errors were encountered: