/
DFS 11.1 - Breaking Changes

DFS 11.1 - Breaking Changes

With this version there is a breaking change that must be considered when upgrading from a version before 11.1.

Mediahandler

In digizuite DAM 5.10 the transcode system has change https://digizuite.atlassian.net/wiki/spaces/DD/pages/3708157997. What that means for the DFS connector is that, when requesting rendition that hadn’t been generated yet a fallback image will be returned and the statuscode is 202 (Accepted). The fallback image is of type svg and controlled by Digizuite. Once the rendition is ready in Digizuite is will be served to the mediahandler in Sitecore.

Resizing

The logic when resizing in the mediahandler has changed. In the previous version the resizing was done in code, first we downloaded the image into memory and resized the image. In this version the rezising har moved to Digizuite. We now call a new endpoint at Digizuite that handles the resizing. This also means that if the excact resized rendition requested hadn’t been generated yet a fallback image will be returned, as the above section.

Related content

DFS 11.1 - Upgrade from DFS 9.x or 10.x
DFS 11.1 - Upgrade from DFS 9.x or 10.x
Read with this
DFS 9.2.0 - Release notes
DFS 9.2.0 - Release notes
More like this
DFS 11.1 - JSS Integration - Next.Js - Connect JSS application to Sitecore
DFS 11.1 - JSS Integration - Next.Js - Connect JSS application to Sitecore
Read with this
DFS 9.0.0 - Release notes
DFS 9.0.0 - Release notes
More like this
DFS 11.1 - 5 Setup Digizuite DAM
DFS 11.1 - 5 Setup Digizuite DAM
Read with this
DFS 11.0 - 8 Serving media
DFS 11.0 - 8 Serving media
More like this