en	DCE record

en	This record defines how the new content element type should look like.

en	Here you name the new content element type. You can use "LLL:" references here.

en	The identifier is used for CType of new content elements based on this DCE. The identifier you enter is prefixed with "dce_". If the identifier remains empty, the uid of this DCE is used for CType. The identifier must be written in lowercase, undercores are allowed.

en	When you disable this DCE, all content elements existing based on this DCE, will get also hidden. Otherwise they would cause errors, because disabled DCEs can not get rendered.

en	Here you can define dynamically fields and arrange them in tabs. Those fields can get used in templates.

en	You can outsource the template to a file or edit the template right here in the inline editor.

en	Here you edit the Fluid template for the frontend output of this DCE.

en	Here you need to set the path to a template file. Files can be used directly from e.g. fileadmin/, but you can also enter paths like "EXT:mytemplate/.../MyDce.html".

en	When you enable this option, all DCEs of same type in a row will get wrapped by a container template.

en	When the container item limit is set, a new container will be forced when the limit is reached.

en	You can outsource the template to a file or edit the template right here in the inline editor.

en	Here you edit the Fluid template for the container wrapped around the instances of this DCE.

en	Here you need to set the path to a template file. Files can be used directly from e.g. fileadmin/, but you can also enter paths like "EXT:mytemplate/.../MyDce.html".

en	This enables the simple backend view. When you uncheck this you get a backend Fluid template for custom backend output.

en	Choose the field in this DCE which should be displayed as header in backend's page view.

en	<p>Here you can define a symfony expression, to define the DCE fields you want to use as header. All field variables are available.</p> <p>You can concatenate multiple fields, like this: <code>firstName ~ ' ' ~ lastName</code></p> <br> <p>With <code>contentObject['uid']</code> you can access the tt_content row, to e.g. fetch the uid.</p> <br> <p>Also the DCE instance itself is available, e.g.: <code>dce.getTitle()</code>.</p>

en	When enabled, you get an input field where you can enter a Symfony expression, instead of a select dropdown.

en	Here you can select several fields from your DCE. They get displayed in a table. With support of images.

en	You can outsource the template to a file or edit the template right here in the inline editor.

en	Here you edit the Fluid template for the backend output (in page module) of this DCE. Please use provided "BackendTemplate" layout, which provides sections for "header" and "bodytext".

en	Here you need to set the path to a template file. Files can be used directly from e.g. fileadmin/, but you can also enter paths like "EXT:mytemplate/.../MyDce.html".

en	Which icon should the DCE have in backend? You can choose "custom" to upload your own icons.

en	Enter the path to your custom icon.

en	Should this DCE also be displayed in wizard for new content elements?

en	The wizard for new content elements provides tabs for different categories. Here you can choose in which tab this content element should appear.

en	Description displayed in new content element wizard. You can use "LLL:" references here.

en	This allows you to render a different frontend template, when a configured GET parameter is containing the uid of a certain tt_content element based on this DCE.

en	This is the GET parameter which is checked. The given content element will render the detail template, if this request parameter is given.

en	<p>Here you can define a symfony expression, to define the DCE fields you want to use as slug. All field variables are available.</p> <p>You can concatenate multiple fields, like this: <code>firstName ~ '-' ~ lastName</code></p> <br> <p>With <code>contentObject['uid']</code> you can access the tt_content row, to e.g. fetch the uid.</p> <br> <p>Also the DCE instance itself is available, e.g.: <code>dce.getTitle()</code>.</p> <br> <p><b>Keep in mind:</b> Slugs on same page must be unique! And you need to apply an additional Routing Enhancer configuration.</p>

en	Same as slug expression, just for the page title of the detail page. The page title get not sanitized, like the slug.

en	When you've defined a slug expression for page title and enable this option, the expression is applied as page title. You can prepend, append or overwrite the current page title.

en	You can outsource the template to a file or edit the template right here in the inline editor.

en	Here you edit the Fluid template for the detail page output of this DCE, which is triggered by configured GET parameter.

en	Here you need to set the path to a template file. Files can be used directly from e.g. fileadmin/, but you can also enter paths like "EXT:mytemplate/.../MyDce.html".

en	If you disable the DCE cache, it may impact your page render performance.

en	When enabled, it bypasses fluid_styled_content (lib.contentElement). This disables the "csc-default" wrap in html output and increases performance significantly.

en	Flexforms can have a separate title. The configured default LLL key points to "Contents:"

en	If enabled, a new "Access" tab is displayed in content elements. Visibility fields get automatically removed from DCE palette, if configured.

en	Displays "Media" tab in content elements. You can access the media in your Fluid template with: {contentObject.media} or {contentObject.assets}

en	Displays "Category" tab in content elements. You can access the categories in your Fluid template with: {contentObject.categories}

en	Above the flexform field there is a TCA palette containing several TCA fields, in each content element. Here you can define the TCA fields to be displayed.

en	Define a path to be added to Fluid layout root paths. This affects all templates of this DCE.

en	Define a path to be added to Fluid partial root paths. This affects all templates of this DCE.