Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
2.5.9
-
None
Description
Context
- In the translations app: When you export the translations for a site, only basic textfields are considered
- But most of our used fields are based on custom types
- Thus for a test-page only ~600 of more than 3000 fields got into the exported excel
- To fix this, we added a decorator for the list of types which are included and added our custom types here. But this was nasty and from now on whenever we add a new custom type we also have to add it in the decorator list. This might lead to missing value over time
Use Cases
- Authors want to export whole sites as Excel-files, add all the translations in every line, and the import it again. So they don't have to click into every dialog and add translations there. That would be much slower.
Current Status
Proposal
- The translation export/import should use fields of any type (including custom types) by default
Checklists
Acceptance criteria