...
PROD environment migration guide
| Info |
|---|
If you followed the steps in https://digizuite.atlassian.net/wiki/spaces/DD/pages/edit-v2/3710091372#Manual-migration-guide, you can ignore this section. If the prod migration is based on a test setup, however, this does need to be done - and only this section. |
In some cases, new formats might be created and mapped to old media formats without running the migration script in the previous section.
...
To migrate the renditions based on existing formats and their mapped media formats, please run the following script: https://github.com/Digizuite/scripts/blob/
...
LaxSecurity destinations
In the old transcode system, it was possible to generate renditions and make them available at specific destinations via asset type configurations or profiles. If a destination was configured with LaxSecurity set to true, the renditions stored in this destination would be publicly available.
...
Although not strictly necessary, the introduction of the new transcode system provides a good basis for revisiting the formats that are defined for existing customers. Maybe some of the old media formats are no longer needed. Maybe some of the automatically mapped formats can be mapped better manually, for instance, utilizing the support for webp and transparency.
DFO or other search-based integrations
If a customer is using a DFO integration using GetEpiserverAsset, you will need to build a new search index. You can do this by changing an output parameter to have tooltip enabled, saving and rebuilding.
This is also required for other search2 searches that are used by integrations, that are returning assetstream urls.
Renditions are stored in a new table after migrating to the new transcode system, which search2 will not know about unless it is rebuild. Therefore if it is not rebuild, the search will not return the new formats.