Bulk translations import/export

When do you need this

When you are setting up Peripass for the first time.
When you are configuring new parts of Peripass that contain a lot of translations.

The import export functionality is not optimized for novice users of Peripass. It expects a good knowledge about all the translations and their meanings in Peripass.

Main idea

Export all translatable fields in Peripass. Also translations that are not provided (yet) are exported, however only for the languages configured.
Import new translations. It is possible to import a limited set of translations. All translations imported will be overwritten. Not imported translations won’t be touched.
Export history: in order to recover in case of mistakes, it is possible to re-download a previous export.
Where to find: under general settings

Known limitations and checks on import

It is not possible to upload an embedded image as base64. Images should be uploaded once manually, so that a hosted url is available.
If translations are too long, the export will result in a translation named “!!! TRANSLATION TOO LONG !!!”. It is not possible to import a translation with this name, to avoid erroneous overwrites.
The import will check for duplicate entries.
Be aware that the adding/removing configuration in Peripass can alter the different available translations. This will render historical exports useless without a lot of manual tweaking. E.g. adding a new self service kiosk will create a bunch of new translations. Removing one will result in a lot of object id’s not being recognised anymore.
The import will fail if the filename contains multiple dots. (ex. 'import.2024.xlxs' is not supported)