DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
DAM for Content Elements¶
Author: | Kasper Skårhøj |
---|---|
Created: | 2002-11-01T00:32:00 |
Changed by: | Lorenz Ulrich |
Changed: | 2012-07-20T22:19:14.810000000 |
Author: | The DAM development team |
Email: | typo3-project-dam@lists.netfielders.de |
Info 3: | |
Info 4: |
DAM for Content Elements¶
Extension Key: dam_ttcontent
Copyright 2003-2012, The DAM development team, <typo3-project- dam@lists.netfielders.de>
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.com
Table of Contents¶
DAM for Content Elements 1
Introduction 1
Installation 1
Reference usage 1
Captions 2
Introduction¶
This extension provides some functionality for the default content elements (tt_content). While generally new content elements should be developed to support the DAM features, this extension can help to use a few features of DAM with the default content elements.
Installation¶
The extension manager shows several options during installation. All options should be self explanatory. For more informations of the provided functionality have a look in the following sections.
Reference usage¶
The DAM system allows to use file references instead of the normal copy mechanism TYPO3 uses to bind files to content elements. The extension Content/DAM reference usage (dam_ttcontent) is an example for that functionality.
The extension provide the reference functionality for image files for the content elements Image and Text w/image . This is done by adding a field to these elements that allow to insert images as reference.
For frontend rendering this extension just add some TypoScript to the content elements rendering setup which passes the filenames to the rendering code.
Administration¶
The extension just add a field in TCA and add some TypoScript setup to fetch the filenames for that field and pass it to the TS rendering setup. The rendering itself is not done by this extension. Therefore the principle can be adopted to all other content elements or plugin records.
Important: When you use another extension which changes/replaces the image rendering already this solution might break the rendering so you have to adopt the TypoScript setup for the rendering setup.
See ext_localconf.php for a functionality sample.