FileMultiple¶

sFileExtAllowed¶

Comma-list of file extensions that are allowed for uploading.

Example:

jpg, jpeg, bmp, gif, png, ai, pdf, ico

sFileExtProhibited¶

Comma-list of file extensions that are not allowed for uploading.

Example:

exe, bat, com

Wait, what? Why do I have to set a list of allowed and a list of prohibited file extensions? Well, you don't! You either allow everything (do not set sFileExtAllowed) except the ones listed in sFileExtProhibited. Or you prohibit everything (do not set sFileExtProhibited) except the ones listed in sFileExtAllowed.

By the way: If an extension is listed in both configurations, it is allowed.

By the way 2: If both configurations are set but the extension in question isn't listed in either one of them, it is prohibited.

nMaxCount¶

Number. Maximum amount of files to be used. -1 unsets the limit.

nFileMaxSize¶

Number. Maximum size per file in megabytes. -1 unsets the limit.

bOverwriteExistingFiles¶

Boolean. If set, files that already exist, will be overwritten. If set to false, a new name will be found and that name is written to the database of course.

sUploadDir¶

String. Path where to put the files.

Example:

uploads/tx_mhomsqlio/

sConcatenate¶

String. Now think of the uploaded files being outputted in a normal or detail view. How would you like to chain multiple images together? Default is a simple comma but you might change that here.

Example: ::

,

sConcatenateRaw¶

String. See sConcatenate. This is pretty much the same except that this chaining string is used whenever we need a raw output (at the moment, only CSV files are built upon raw outputs).

bSaveFullPathsInsteadOfFilename¶

Boolean. Specifies how the filenames are written to the database. If set to true, full paths from the TYPO3's main directory (/) are saved, simple filenames without any path otherwise.

If you don't know what to do or are free to choose as you just set that up, save only the filenames (set this option to false).

sFileDelimiter¶

String or character. Define, how multiple filenames are split inside the database. Common values here are comma or semicolon.

Example:

,

bSaveInto1nTableInstead¶

By default, the filenames (with or without paths) are saved into the same table the current SQL Frontend is listing. Anyhow, you might want to change this and write the filenames into a separate, related (1:n) table. If so, set this boolean setting to true and configure the following options starting with sFile as well.

If you save into a 1:n-relation table, the current column this configuration is placed upon holds a number that indicates the amount of related entries inside the 1:n-relation table. This is TYPO3-generic behaviour.

sFile1nTable¶

String. Name of the relation table. Example:

tx_news_domain_model_media

sFile1nTableFileColumn¶

String. Column inside the relation table into which the single filenames (with or without paths) are written.

Example:

image

sFile1nTablePidColumn¶

String. Column inside the relation table which holds the parent ID (being the ID that points towards the current SQL Frontend table).

Example:

pid

sFileMainTableKeyColumn¶

String. Column inside the current SQL-Frontend-shown table that holds the own ID. This is the column that sFile1nTablePidColumn points to.

Example:

uid