Configuration

Reference

Constants

Properties of plugin.media2click. Use the Constant Editor to change these settings:

enable

Property:
enable
Data type:
boolean
Description:
Enable the extension’s functionality
Default:
0

disableCObj

Property:
disableCObj
Datatype:
comment
Description:
Disable the cObject / FLUIDTEMPLATE rendering, switch back to classic rendering instead
Default:
#

allWrap

Property
allWrap
Data type:
wrap
Description
Additional wrap to all placeholder content (only used with classic rendering)
Default:
<div class=”media2click-placeholder-inner”>|</div>

showTitle

Property:
showTitle
Data type:
boolean
Description:
Enable display of the video’s title as the palceholder’s title
Default:
1

showPreviewImage

Property:
showPreviewImage
Data type:
boolean
Description:
Enable display of the video’s preview image
Default:

1

Properties:

maxWidth: integer
Maximum width
maxHeight: integer
Maximum height

templateRootPath

Property:
templateRootPath
Data type:
String
Description:
Path to your Fluid templates when using the FLUIDTEMPLATE cObject rendering

partialRootPath

Property:
partialRootPath
Data type:
String
Description:
Path to your Fluid partial when using the FLUIDTEMPLATE cObject rendering

layoutRootPath

Property:
layoutRootPath
Data type:
String
Description:
Path to your Fluid layouts when using the FLUIDTEMPLATE cObject rendering

TypoScript Setup

All configuration is forwarded to the renderer classes via the settings of the corresponding FLUIDTEMPLATE and the additionalConfig attribute of the Fluid media viewhelper. Therefore all settings are not interpreted as TypoScript, but just used as is. It’s not possible to use additional TypoScript to dynamically change these attributes.

For FluidStyledContent content elements, everything has to be set up in lib.contentElement.settings.media.additionalConfig.

For the News extension, use plugin.tx_news.settings.detail.media.video.additionalConfig.

As stated above, there is no interpreting of TypoScript inside a FLUIDTEMPLATE’s settings. So you can not use the reference operator ‘=<’ to reuse the settings of lib.contentElement in another FLUIDTEMPLATE, but have to use the copy operator ‘<’.

These parameters are available:

enable2click

Property:
enable2click
Data type:
boolean
Description:
Enable the extension’s functionality. Set via Constant Editor.
Default:
0

placeholderContent

Property:
placeholderContent
Data type:
Array
Description:

parent attribute to all settings regarding the content of the placeholder

Properties:

.allWrap:
This wraps the whole placeholder content. (only used with classic rendering)
.value: String
Default text (only used with classic rendering)
.lang: Array
Array of language keys, defining optional language specific values (only used with classic rendering)
.wrap: wrap
This wraps the content. (only used with classic rendering)
.showTitle: boolean
If enabled, the Fluid media tag’s title attribute is shown as the palceholder’s title. Set via Constant Editor.
.titleWrap: wrap
This wraps the title. (only used with classic rendering)
.showPreviewImage: boolean
Show preview image if available. Set via Constant editor.
.previewMaxWidth: integer
Maximum width of preview image. Set via Constant Editor.
.previewMaxHeight: integer
Maximum height of preview image. Set via Constant Editor.
.cObject: cObject

If present, this cObject is used for rendering the placeholder. If this cObject is a FLUIDTEMPLATE, some useful values are passed to the fluid template as settings:

.settings:

Settings for the FLUIDTEMPLATE cObject

Default properties:

.videoProvider: String
Provider of the video, i.e. “YouTube” or “Vimeo”. Usefull to adapt the placeholder content, i.e. link to the proper privacy statement.
.showTitle: boolean
see above
.title: String
The title of the video
.width: integer
The calculated width of the video iframe
.height: integer
The calculated height of the video iframe
.previewImage: String
Path to the preview image relative to the web root