Closed lenvanessen closed 7 years ago
Currently, to translate a template specific field you define this in the translateselect.
Ideally, you want to be able to define this per template-specific field since this is more consistent and gives you more control.
I think that this would be really hard to do without changing how the fields are saved in bolt core... My plan was to hold out for the "successor" to template fields that is still planned for 4.0.
Agreed
Currently, to translate a template specific field you define this in the translateselect.
Ideally, you want to be able to define this per template-specific field since this is more consistent and gives you more control.