Back to Table of Contents

Basic Configuration¶

Extension Manager¶

After installation you can configure the DAM in the extension manager.

Important note for upgraders: If you are upgrading DAM from a version prior to 1.1 you need to reconfigure both dam and rtehtmlarea:

• In the configuration options of dam, enable the media tag and the htmlArea RTE integration.
• In the configuration options of rtehtmlarea, disable the above mentioned features.

You see several options here:

Setup
TSconfig setup defining modules functions and indexing behaviour.

Enable Web->File
When DAM is installed all file operations go through DAM. A new module appears in your main menu called Media. The Web->File module is hidden.

If you want to reenable the traditional File module, go to the Extension Manager, click the title Media (DAM) and check Enable Web>File.

Caution: DAM will not be aware of files uploaded through the traditional File module, so this might cause inconsistencies and confusion.

Hide Media Sysfolder
DAM creates a folder to store all the media records. Normally all the operations on the media records can be done through the Media menu.

You can hide the Media Folder by setting a default user TSConfig. Thus, no user (not even admins) will be able anymore to edit the dam tables in the List, which might be a wise move, because editing file names and the like will inevitably cause mistakes. Hiding the media folder also reduces clutter. So it is recommended to hide the media folder, but of course only after you have granted access to that page via Web>Access as described in chapter 'Setup DAM-Backend-Permissions'.

media tag
This adds the tag <media> to RTE content processing and frontend rendering. This is needed to create files links using DAM references. Additional page TSconfig may be needed to enable the media tag. This tag is similar to <link> with the difference that the given id is not a page but a media id.

Depending on the load order of installed extensions it may be needed to manually add the media tag processing to the RTE processing rules in page TSconfig:

## Add txdam_media to RTE processing rules
RTE.default.proc.overruleMode = ts_css,txdam_media
## Use same RTE processing rules in FE
RTE.default.FE.proc.overruleMode = ts_css,txdam_media
## RTE processing rules for bodytext column of tt_content table
RTE.config.tt_content.bodytext.proc.overruleMode = ts_css,txdam_media
RTE.config.tt_content.bodytext.types.text.proc.overruleMode = ts_css,txdam_media
RTE.config.tt_content.bodytext.types.textpic.proc.overruleMode = ts_css,txdam_media

Why is the media tag needed?

This is because it wouldn't be possible to link assets by reference. This means whenever a link to a file is created in the RTE the file path is saved. But when the file is renamed or moved this reference is lost. The media tag use the media id instead (tx_dam.uid) and the file link will be created while FE rendering.

Activating the media tag in the EM extension options will also install a transformation handler which overrides the default ts_links mode (used also when ts_css shortcut is configured). Processing of links in db direction will be done by that handler, which searches for linked files in A tags that can be substituted with a media tag.

The media tag will be rendered in the frontend by the plugin plugin.tx_dam_tsfemediatag which is registered in the TypoScript setup of lib.parseFunc.tags and lib.parseFunc_RTE.tags.

plugin.tx_dam_tsfemediatag {
    procFields {
      file_size = 1
    }
    tag {
      current = 1
      typolink.parameter.data = parameters : allParams
      typolink.extTarget = {$styles.content.links.extTarget}
      typolink.target = {$styles.content.links.target}
      typolink.title { 
        dataWrap = { field : txdam_file_name } ({ field : txdam_file_size })
        htmlspecialchars = 1
      }
      parseFunc.constants =1
    }
  }

lib.parseFunc.tags.media = < plugin.tx_dam_tsfemediatag
lib.parseFunc_RTE.tags.media = < plugin.tx_dam_tsfemediatag

As you see the fields from the tx_dam table are available in the typolink setup prefixed with txdam_. While the setup is very similar to the default link tag setup, the used typolink function is NOT the one available in stdWrap but has more or less the same properties.

htmlArea RTE integration
If set and if the htmlArea RTE extension is installed, the DAM media browser will be used by the Insert image and insert file link dialog.

Developer/Debug Functions
This activates special functions for development and debugging. This should stay deactivated for normal usage!

When you install DAM and it's co-extensions the following are made to your backend.

3) Some changes in RTE configuration: