DAM

1.5.9. FAQ

Q: The TSconfig option hideRecords to make the Media SysFolder invisible does not work

A: Upgrade to TYPO3 4.0.3

 

Q: I get following error message: 'Meta record could not be inserted: Attempt to insert record on page 'Media' (31) where this table, tx_dam, is not allowed'

A: Change the Media folder to the page type 'SysFolder' this conversion should be happen automatically when selecting the details view of the dam extension in the Extension Manager.

 

Q: File names are truncated. How can I change that.

A: The file name length is limited. The maximum length can be increased in the install tool setting the property [SYS][maxFileNameLength] to a higher value.

 

Q: The upload module show x Mb for the maximum upload size. Why?

A: The size of the file upload is limited. The maximum size is a result of different settings in PHP, TYPO3 and the web server (Apache). In TYPO3_CONF_VARS the maximum file size can be configured with by [BE][maxFileSize]. But this has no effect when PHP settings are lower. Make sure the settings of upload_max_filesize and post_max_size in php.ini are big enough. The resulting maximum upload size is for the whole upload and not for a single file. That means an upload will fail with multiple files even when every single file is smaller than the maximum upload size but the sum of the file sizes exceed that limit.

 

Q: When saving a translation of a meta data record I get following error message: 'These fields are not properly updated in database: (...) Probably value mismatch with fieldtype.'

A: It seems that TYPO3 is configured to use the charset UTF-8 but the database connection is not properly configured. In the install tool the property [SYS][setDBinit] needs to be configured as follows:

  SET NAMES utf8 ;

  SET CHARACTER SET utf8 ;

  SET SESSION character_set_server=utf8 ;

  SET SESSION character_set_client=utf8 ;

  SET SESSION character_set_connection=utf8 ;

Q: How do I enable file referencing?

A: Just install dam and dam_ttcontent. Upon installation of dam_ttcontent you will have some options on where the "references" will apply.

 

Q: Once enabled, is it enabled for all content elements and extensions?

A: The dam_ttcontent simply modifies the TypoScript for the rendering of the tt_content "imgtext" and "image" content objects. So any other extension or content elements are unaffected by this. If you want to do that in your extension, just follow the example in dam_ttcontent (you just need to get the list of files from a field through an API-call to DAM).

 

Q: What about the files which were used in content elements prior to enable file referencing? Will they continue to use the file copy in uploads/ or can they be automatically 'converted' to use the original files in fileadmin/? If not, would I really have to re-import them in every content element that I use?

A: Either you use the copied files, or you use the references to DAM objects. I don't think there is currently a way to "migrate" information from old tt_content-hardcoded image paths to DAM-objects.

 

Q: When I select a file (f.e. 'filename.xxx') to add it to my news, DAM creates a copy to "uploads/media/" and name it 'filename_01.xxx'. If I add it again, DAM creates a second copy 'filename_02.xxx'. How can I disable it?

A: That has nothing to do with DAM!! The behavior of normal image form fields in content elements or any extension is not changed, and cannot be changed. So copying to uploads/media/ is the default TYPO3 functionality of file handling. To use file references in an extension, the extension needs to be adapted to use DAM.

 

Q: The file icons in the Media modules are shown as '?' when access options are set for the record (hidden, start, stop, ...).

A: The icons are rendered on the fly. Make sure the image processing options works in the install tool and following option is set to 0:

[GFX][noIconProc] = 0

 

Q: PDF files are rotated sometimes for 90 degrees in thumbnails. How to fix that.

A: This is not a problem of DAM, but of ImageMagick. The same problem occurs when DAM is not installed.

 

Q: And finally: How stable is file referencing?

A: As stable as you want it to be. It works, and its a pretty simple concept, as it uses "standard" TYPO3 features: fields with MM-relations to other objects (for the "reference") and userFunc for the TypoScript part that will handle the rendering (for de-referencing the objects back to files). It won't automatically change all your "file" fields into "reference" fields, you have to do that on your own in your extensions.