Magnolia 5.3 reached end of life on June 30, 2017. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

This page is about (warning) DAM 1.x. The way assets are registered and used changed. If you work with (warning) Magnolia 5.3+, see Digital Asset Management module .

The Digital Asset Management module 1.x installs the Assets app 1.x. For more information about working with the DAM see Digital asset management.

The Digital Asset Management (DAM) module provides the functionality to manage assets such as images, videos and documents and use them on the website. The module installs the Assets app 1.x.

Using

See Digital asset management on how to use the features provided by this module.

Download

The DAM module is bundled with Magnolia and typically already installed. You can download it from our Nexus repository.

Installing

Digital Asset management is a Community Edition module. It is typically already installed. Launch the Configuration app and go to /modules/dam to check.

Unable to render {include} The included page could not be found.

Uninstalling

Unable to render {include} The included page could not be found.

Configuration

The DAM is configured in /modules/dam:

Node nameValue

 dam

 

 apps

 

 config

 

 dialogs

 

 commands

 

 fieldTypes

 

Folders:

Media types

The DAM supports the following media types: imageaudiovideodocumentflash and application

Media types are configured in the /dam/config/mediaTypes node. The link between the MimeType and the MediaType is done by configuration and RegexVoters. For more information see Renditions and media types.

Here's an example configuration for the audio media type.

Node nameValue

 dam

 

 config

 

 mediaTypes

 

 audio

 

 voter

 

 class

info.magnolia.dam.util.RegexVoter

 pattern

audio/.*

Content disposition

It is possible to configure the handling of Content-Disposition headers for all content in the DAM in the /dam/config/contentDisposition node. By default the DAM is configured to not serve the Content-Disposition header for flash and video files. All other content is served with the Content-Disposition header enabled by default. If you need to disable serving content with Content-Disposition header for other content types, add their MIME types to /dam/config/contentDisposition/contentType/rejected.

Node nameValue

 dam

 

 config

 

 contentDisposition

 

 contentType

 

 rejected

 

 1

application/x-shockwave-flash

 2

video/mp4

 class

info.magnolia.voting.voters.ResponseContentTypeVoter

 class

info.magnolia.voting.voters.VoterSet

To disable serving the Content-Disposition header based on path follow these steps:

  1. Create a new node inline under contentDisposition.
  2. Under the new content node, create three property nodes:
    • class and set the value to info.magnolia.voting.voters.URIStartsWithVoter.
    • pattern and set the value to /dam/inline.
    • not and set the value to true.

This will configure all files in folder inline to be sent without content disposition headers. The new content node should look like this:

Node nameValue

 contentDisposition

 

 inline

 

 class

info.magnolia.voting.voters.URIStartsWithVoter

 not

true

 pattern

/dam/inline