What does it do? 

With this extension, you can easily create new dynamic content elements.

In opposite to native content elements (like fluid_styled_content or content_blocks), DCEs are based on FlexForms. FlexForms allows you to define dynamic content structures, without the need to extend tt_content database table.

Goals of DCE 

• Make it easy to create new custom content elements
• With as many configurable fields as you want
• Flexible and comfortable templating for each CE (using Fluid)
• A lower learning curve for editors (using customized content elements)
• and for integrators as well, who start with TYPO3 CMS

DCE Features 

• Over 15 years of experience
• Hundreds of installations per day in TYPO3 CMS projects

Requirements 

• TYPO3 14.3 or newer within the TYPO3 14 release line
• PHP 8.2
• PHP extensions DOM and JSON

With composer 

Require DCE on the command line:

$ composer req t3/dce:"^4.0"

Composer installs and activates DCE automatically. Afterwards, set up the extensions and apply the required database schema changes:

$ vendor/bin/typo3 extension:setup

Without composer 

You can also fetch DCE from TER and install it without Composer. Import and activate the extension through System > Extensions.

DCE provides no further options here.

Overview 

First, you need to login to TYPO3 backend with administrator privileges. Those are required to create or edit DCEs. Content elements made by DCE, can be also used with regular editor privileges.

You'll find DCE under "Admin Tools" in the main menu. It shows you a list of all DCEs existing in the database:

Create your first DCE 

Click the button "Create new DCE" and enter the title of your new dynamic content element. For example: "Teaser".

Also, we set the identifier to "teaser". Later this will be prefixed with "dce_" and used as CType of this new content element.

Now, create a new field, keep the default type "Element" and enter "Title" as field title. Set variable to "title".

As configuration we choose the option "Simple input field" from the dropdown above the configuration textarea. It pastes a sample configuration with commonly used settings. You should get this output:

Now, add another new field with the title "Description" and "description" as the variable name. As configuration we use "RTE" from the dropdown box.

Next, create the last field with the title "Images" and the variable name "images". As configuration we use "File Abstraction Layer" from the TYPE: FAL group. It inserts a TCA type=file configuration with options such as the minimum and maximum number of images.

Save the changes. You should see the structure of your first DCE:

Now, when you clear the system caches, you can already use the content element on your pages:

Frontend Templating 

Let's return to your Teaser DCE and switch to tab "Template". You see a default template, which will be output in frontend for each instance (content element) of this DCE.

In this editor, you can define what TYPO3 should display, right in place. You can also load template files if you want.

The dropdown above the template field shows different items you can choose from. It displays the fields you have defined and some other very helpful stuff:

Now, we build the frontend output that we want, for each content element based on this DCE. The template engine here is Fluid:

<div class="dce">
    <h2>{field.title}</h2>
    <div><f:format.html>{field.description}</f:format.html></div>
    <f:for each="{field.images}" as="image" iteration="iterator">
        <f:image image="{image}" alt="{field.title}" maxHeight="100" />
    </f:for>
</div>

We use variables pointing to the fields we've defined before, e.g. {field.title}.

When you want to output HTML, you need to use format.html view helper of Fluid. You can use it like in the example above, or inline: {field.description -> f:format.html()}. Also, we use the for view helper in Fluid to iterate over {field.images}. It's an array of FileReferences, which can get directly passed to the image view helper.

When we save the DCE, clear the system caches (!) and create a new content element based on this DCE, we see this output (in backend and frontend):

The Backend View 

So far we have defined the fields of our content element and the frontend output. But how is the content element displayed in the backend?

Well okay, it displays the title of the DCE we have defined. But we do not see any differences when we have two of these content elements on the same page. Let's change this, by configuring the Simple backend view in Backend Template tab.

Here you can define which (single) field should be displayed as header (and label in list view). And which fields should also get displayed in bodytext. When we choose all options from bodytext field (but DCE title), we get more info about our content element instances:

This saves much time and helps you to build fast new content elements.

DCE Container 

Until now, you know the very basics of how DCE works. Let's use a more intermediate feature as of the last step in this tutorial, which is potentially helpful for you: DCE Container

First, let's see the output of our content elements in the HTML source code of frontend output. We have placed two content elements on a page:

When we compare this HTML source with the Fluid template from above, we will see our code, with filled placeholders. Each content element is wrapped with <div class="dce"></div>, because we have defined it in our template.

DCE Containers help you to wrap all those standalone elements with a custom container template. First, you need to enable the feature:

Just by enabling the feature (and clearing the caches) we see an instant effect in HTML output:

We see two wraps:

• dce-container This comes from the container template itself
• tx-dce-container This is because we use the DefaultContainer Fluid layout (which is optional)

Also, the backend view has been upgraded, it displays a color (calculated based on uid of the first element in the container):

What's next? 

Congratulations! You know how to create a first content element in DCE.

Check out the next section in the documentation Users manual to get an overview of the options and possibilities DCE gives you.

Have fun! And when you have questions, check out the Support section :)

Title 

This is the name of the DCE, which is also shown in the type selection of a content element. You can point to LLL: references here and translate the title for different languages.

Identifier 

The identifier is used to generate the CType for content elements based on this DCE. Enter the identifier without the dce_ prefix. For example, the identifier what_ever generates the CType dce_what_ever. When the identifier remains empty, DCE generates dce_dceuid<uid>. The identifier must be lowercase; underscores are allowed.

Examples for values entered in the identifier field: teaser or what_ever.

Inactive 

When the DCE is inactive or hidden, it is not shown as the type when a content element is created. It is only shown in the DCE BE module.

Fields 

In the fields section, you can add a number of different fields that this DCE should contain. A DCE can be saved without fields, but no usable CType or TCA registration is generated until it contains at least one active field.

A field has three types available:

• Element This is a field in your new content element, like a text field, a checkbox, an image or a whole rich text editor (RTE). The composition for this field is done in the configuration. You can use field types and options supported by TYPO3 FlexForm data structures.
• Tab This creates a new tab register. All fields that are defined below this tab are shown in BE on a new tab page. You may also rename the first "General" tab by creating a tab as the first item.
• Section It is highly encouraged to not use sections anymore! Check if DCE Container can help you or use EXT:container for your purposes.

Common to all types is the title field, where you define a speaking label for the editor. You can use an LLL: reference here. A Tab also has a required variable, which is used as its FlexForm sheet identifier, and can be marked as inactive.

Field options 

For the default type Element you have to define a title (with LLL: support) and a variable name which is to be used in the Fluid template. Variable names have to be written in lowerCamelCase and the variable names must be unique inside each DCE.

Note

The configuration for the fields is stored in FlexForm (XML) format. Look for <el> in the FlexForms section of the T3DataStructure documentation to get detailed information for the definition of the field configuration.

To make it a bit easier there is a handy select box provided with the most used possible input field types. If you select one entry the corresponding FlexForm XML code is inserted in the configuration input field.

For fields which use the TCA types group, select, inline or file, there are additional configuration attributes provided by DCE available.

dce_load_schema 

<dce_load_schema>1</dce_load_schema>

Copied!

When adding a group field and link it with e.g. News (by Georg Ringer), then the field contains a comma-delimited list with uids of the selected news. That is not very useful in Fluid templates.

But when this attribute is activated, the used table is inspected. If an Extbase model and repository exist for this table then the repository is instantiated and a findByUid() is called for every uid. The complete Extbase models are then taken over to the Fluid template (as an array).

If the table is not part of an Extbase extension, the corresponding record is loaded from the database and handed over as an associated array.

Note

Automatic Extbase model and repository resolution is intended for one table. Group fields containing records from multiple tables can be resolved by the associative-array fallback when their stored values contain the table name.

Using the table tt_content and adding content elements which are based on another DCE, automatically the corresponding DCE will be loaded and filled. In the template of the second DCE the template of the inserted DCE can be called and rendered:

<f:for each="{field.otherDces}" as="otherDce">
    {otherDce.render -> f:format.raw()}
</f:for>

Copied!

You need to use the raw view helper of Fluid because otherwise the rendered HTML will be escaped. If you use the f:format.html view helper the curly braces get escaped and variables will not be interpreted anymore.

It is also possible to access directly the value of single fields:

{otherDce.get.fieldName}

Copied!

dce_load_entity_class 

<dce_load_entity_class>VendorName\Extension\Domain\Model\YourModel</dce_load_entity_class>

Copied!

Uses this class (and its repository) instead of guessing the model class name from table name.

dce_get_fal_objects 

<dce_get_fal_objects>1</dce_get_fal_objects>

Copied!

This option is evaluated while schema loading is active, so both dce_load_schema and dce_get_fal_objects are required. A field with type=file or a relation to sys_file_reference returns an array of TYPO3\CMS\Core\Resource\FileReference objects. A relation to sys_file returns an array of TYPO3\CMS\Core\Resource\File objects.

dce_ignore_enablefields 

<dce_ignore_enablefields>1</dce_ignore_enablefields>

Copied!

For records loaded through DCE's associative-array database fallback, this option removes restrictions for fields such as deleted, hidden, starttime and endtime. It does not change the query settings of an Extbase repository.

dce_enable_autotranslation 

<dce_enable_autotranslation>1</dce_enable_autotranslation>

Copied!

If you load a page via group field, then always this page is loaded, regardless of the language that is just used. Using this attribute shows the translated page if it exists.

For pages, DCE uses TYPO3's getPageOverlay() handling. For other records, it uses getLanguageOverlay().

dce_skip_translation 

<dce_skip_translation>1</dce_skip_translation>

Copied!

When a DCE field got this option set, DCE fields act like l10n_mode => 'exclude' in TCA. Normally FlexForms does not support this behaviour.

In backend, a field with this option set is only visible, when:

• You are on default language (sys_language_uid = 0) or
• the translated DCE content element has no l18n_parent set

To achieve this, DCE modifies the displayCond for the field, in XML configuration - when you already defined some display conditions, they get merged (using <and>).

In frontend, the field value will get overwritten by the field value of the l18n_parent-element, no matter which values are stored in pi_flexform.

This feature is not supported for section fields.

Special Thanks to Silverback (https://silverback.st/) who sponsored this feature!

Template type 

File 

The option File let you choose a file that contains the Fluid content that should be used as the template for this DCE. The file name is selected in the "Template file (fluid)" input field.

This option makes it possible that you put the templates under revision control due to the fact that the files are stored in the file system.

The template file can be referenced using one of the following path types:

• EXT: references a file inside a TYPO3 extension and is the recommended syntax. For example: EXT:my_template/Resources/Private/Templates/Example.html.
• PKG: references a file inside a Composer package. Separate the package name and the path within the package with a colon. For example: PKG:vendor/my-template:Resources/Private/Templates/Example.html.
• A relative path is resolved from TYPO3's public web root. The template file is therefore publicly accessible. For example: fileadmin/templates/Example.html.

The configured value must resolve to a file-system path. FAL link syntax such as t3://file=uid=1 is not supported.

If the configured path is invalid or the file does not exist, DCE treats the template as empty and produces no output.

Inline 

The default template type Inline lets you edit the Fluid template directly in DCE's code textarea in the "Template content (fluid)" field.

No namespace declaration 

The dce namespace is registered globally and does not need to be declared in each Fluid template.

Do not retain the former ArminVieweg\Dce\ViewHelpers namespace declaration. If an explicit declaration is required, use the current namespace:

{namespace dce=T3\Dce\ViewHelpers}
<div class="dce">
    Your template goes here...
</div>

Usually, the namespace line should simply be omitted.

Dynamic Templating 

With the select box in the "Template content (fluid)" section you can insert variables and view helpers into the template. The selected variable or view helper is inserted at the current cursor position in the template.

There are several groups inside the select box, which offers you help to work with Fluid:

• Available variables
• Available base variables
• Famous view helpers
• DCE view helpers

{field.nameOfVariable}

<f:render.text record="{contentElementRecord}" field="header" />

{array -> dce:arrayGetIndex(index:'{iteration.index}')}

{string -> dce:explode(delimiter:'\n')}

<f:for each="{dce:fal(field:'thisVariableName', contentObject:contentObject)}" as="fileReference">
    <f:image src="{fileReference.uid}" alt="" treatIdAsReference="1" />
</f:for>

<f:for each="{field.section}" as="entry">
    <f:for each="{entry.images -> dce:explode()}" as="imageUid">
        <f:image src="file:{imageUid}" width="350" /><br />
        Width: <dce:fileInfo fileUid="{imageUid}" attribute="width" />px
    </f:for>
</f:for>

<dce:format.addcslashes>{field.myVariable}</dce:format.addcslashes>

{field.myVariable -> dce:format.addcslashes()}

{field.text -> dce:format.replace(search: 'foo', replace: 'bar')}

{field.text -> dce:format.stripslashes(performTrim: 0)}

{field.text -> dce:format.strtolower()}

<dce:format.tiny>
    Removes tabs and
    linebreaks.
</dce:format.tiny>

{variable -> dce:format.ucfirst()}

<dce:format.wrapWithCurlyBraces prepend="" append="">{field.myVariable}</dce:format.wrapWithCurlyBraces>

{variable -> dce:isArray()}

{dce:thisUrl(showHost:1, showRequestedUri:1, urlencode:0)}

Enable DCE Container 

Enables/Disables DCE Container feature. This option influences the frontend rendering instantly.

When enabled, all content elements (tt_content) in a row based on this DCE are wrapped with the DCE container template. The content elements "in the row":

• base on the same DCE (with enabled DCE container feature)
• are located on the same pid
• are located in the same sys_language_uid
• are located in the same colPos

Any other content element type interrupts the container.

Container item limit 

You can set an item limit (default: 0 / disabled) to limit the number of content elements a container may have. When the the limit is reached, the next content element starts a new container.

Hide other container items, when detail page is triggered 

When the DCE container and the detail page feature is enabled, this option makes it more comfortable to hide all other content elements, which' detail page template is not triggered.

When this checkbox is enabled, all items in a container are hidden, if one item in the container is triggered by detail page GET parameter. In this case, the container template is still rendered, just with a single item. Other containers are not affected.

Template type 

Like the default frontend template of DCE, you can outsource the code of the container to a file. See supported template file paths for the available path types.

DCE Container template 

This template contains the code of the container wrapped around all DCEs within the container.

<div class="dce-container">
    <f:render partial="Container/Dces" arguments="{dces:dces}" />
</div>

All DCEs in the container are stored inside the variable {dces} which is an array of Dce model instances.

So when you iterate over the dces array (using f:for loop) you can access single field values or render the default template. So this partial is basically this:

<div class="dce-container">
    <f:for each="{dces}" as="dce">
        {dce.render -> f:format.raw()}
    </f:for>
</div>

When the page is rendered in the TYPO3 Visual Editor, each content element is rendered in a separate instance of the container template. In this context, {dces} therefore contains only the current content element. This allows the Visual Editor to recognize and edit each content element separately. Regular frontend rendering is not affected.

Container in backend 

When you are using the Simple Backend View, you get a color mark for each content element:

The colors being used can be adjusted using PageTS (on root level):

tx_dce.defaults.simpleBackendView.containerGroupColors {
        10 = #0079BF
        11 = #D29034
        12 = #519839
        13 = #B04632
        14 = #838C91
        15 = #CD5A91
        16 = #4BBF6B
        17 = #89609E
        18 = #00AECC
        19 = #ED2448
        20 = #FF8700
}

Copied!

By default, DCE provides ten color codes, which are picked based on the uid of the first content element in the container.

Start new container 

In content elements you also got the "Start new container" option when DCE container is enabled:

When this checkbox is enabled, a new container is created, like in the screenshot above. With this, you can interrupt and start containers manually.

Simple Backend View 

The Simple Backend View allows you to define fields you want to display, just by clicking it.

This example looks like this in backend:

Expression for header field 

Since DCE 2.7 you can enable a checkbox, which reveals an input field. There you can use Symfony Expressions to output more than one field in content element's header.

Tip

The header is also used as label (in list view and select dropdowns).

This header expression will - for example - generate the following header: "Teaser: My second teaser"

Note

On this page, you see how Symfony expressions in DCE work: DCE Expression Utility

tx_dce.defaults {
    simpleBackendView {
        imageWidth = 50c

        containerGroupColors {
            10 = #0079BF
            # ...
        }
    }
}

Manual Backend Fluid Template 

When you disable the Simple Backend View, you can enter a template (or reference a file using one of the supported template file paths) based on the "BackendTemplate" Fluid layout, which has two sections: header and bodytext

<f:layout name="BackendTemplate" />

<f:section name="header">
    <strong>{dce.title}</strong><br>
</f:section>
<f:section name="bodytext">
    Your backend template goes here...
</f:section>

DCE icon 

The icon that is displayed in front of the entry in the wizard list can be chosen from a large number of available icons. You can also choose "custom", which displays a new field to select the custom icon.

The icon also applies to CType icon.

Custom icon 

If none of the included icons fits your needs, enter a valid icon resource path, preferably EXT:your_extension/Resources/Public/Icons/YourIcon.svg. DCE does not upload the file or enforce specific dimensions.

Show DCE in content element Wizard 

When this option is enabled then an entry for this DCE is added to the list of the New Content Element Wizard.

Wizard category 

You can select here in which category of the wizard the DCE should appear. Besides a new category "Dynamic content elements" also the TYPO3 own categories are available.

Wizard description 

This is a short description text which is shown in the wizard and should describe what is the function of this content element. It can be also be left empty.

Enable detail page 

To enable the functionality for using a detail page you have to check this option.

Detail page identifier (GET parameter) 

This is the parameter which must be used in the GET parameter of the URL to enable the display of the detail page. The value of this GET parameter must be the uid of the displayed content object, to trigger the detail page template.

You should avoid using a parameter name, which is already in use, like "id", "type" or "L".

Slug expression 

Since DCE 2.6.0 a detail page can have a beautiful URL, thanks to TYPO3's routing enhancer, available since TYPO3 v9. This slug expression field controls how the slug is being build.

You can choose a single field or multiple, thanks to Symfony's expression language.

A registered routing enhancer configuration is required, to use this feature. There is a dedicated chapter for this, checkout Faking detail pages.

Page title expression 

This expression is evaluated in the same way as the slug expression, but its result is used for the page title of the detail page.

Use page title expression as page title 

With this option enabled, the current page title is modified based on the page title expression. Unlike slugs, generated DCE detail page titles are not sanitized, for example by converting spaces to dashes.

You can choose between four options:

1. No, keep title as it is (default)
2. Yes, overwrite the current page title
3. Yes, prepend the page title expression output to the current page title
4. Yes, append the page title expression output to the current page title

When selecting "prepend" (3) or "append" (4), the generated DCE detail page title gets separated by a configurable string. By default it separates the DCE and the page title by ' - '.

You can configure this by TypoScript, this is the default configuration DCE ships:

config.pageTitleProviders.dce {
    prependWrap = || - |
    appendWrap = | - ||
}

Those values are used in a stdWrap noTrimWrap function.

Template type 

Like the normal template you can choose between the inline template code and using a template file. The supported template file paths apply here as well.

Detail page template (Fluid) 

Using the inline template type you have to insert the template code in the same manner as for the normal template.

<f:link.page additionalParams="{detailDceUid:contentObject.uid}">
    Show detail template of this content element
</f:link.page>

Helpful links 

• Hide other content elements
• Include detail pages to XML sitemap (EXT:seo)

Cache DCE frontend plugin 

DCE generates the frontend plugin registration automatically when its code cache is rebuilt. This option controls whether DceController::showAction is registered as cacheable or non-cacheable for this DCE.

Direct output 

With this option enabled you bypass fluid_styled_content. Instead of using lib.contentElement, the DCE controller action is used directly. This reduces rendering overhead and removes wrappings defined by Fluid Styled Content, for example <div id="c123" ...>.

This option is enabled by default, separately for each DCE.

FlexForm label 

Defines the text displayed in the content element:

Enable media tab in backend 

This option is only available when EXT:fluid_styled_content is installed. If this option is activated a tab with media (FAL) field is shown in the backend.

You can access the {contentObject.assets} or {contentObject.media} variable in a Fluid template. It contains an array of \TYPO3\CMS\Core\Resource\FileReference.

Enable categories tab in backend 

If this option is activated a tab with category picker is shown in the backend.

You can access {contentObject.categories} variable in Fluid template. It contains an array of \TYPO3\CMS\Extbase\Domain\Model\Category.

DCE palette fields 

This is a list of fields which should be shown in the head area of this DCE in the backend.

Fluid layout and partial root path 

Layouts and partials are a part of Fluid templates and are used to avoid redundancies and keep the code cleaner.

Here you can define Fluid templates folders where to find the layouts and the partials.

With TypoScript you can also set up multiple folder paths for layouts and partials with priority order.

Dashboard 

On the dashboard, you see all DCEs you have created.

You see pieces of information for each DCE:

• Status (enabled/disabled)
• Identifier
• uid

• Usage (amount of content elements using this DCE) - click on it, to see more details

  

• Infos about features used, like DCE container, TCA mappings
• Amount of fields used in this DCE

Also when you have mapped values to TCA columns of tt_content, you get an Update TCA Mappings button, which updates the values of mapped columns, by given FlexForm values.

More stuff 

In the backend module, you also find helpful links to Documentation, Facebook page, etc.

Also, you can clear the system caches, switch to list view and create and edit DCEs.

You can donate and see other donators in the hall of fame.

DceOnCurrentPage 

This user condition checks if the current page contains a content element based on given DCE.

Usage in TypoScript:

[dceOnCurrentPage("teaser")]
    page.10 = TEXT
    page.10.value = The current page contains a teaser DCE.
[END]

You can use either the identifier or the uid of a DCE. The equivalent uid-based condition is:

[dceOnCurrentPage("42")]
    page.10 = TEXT
    page.10.value = The current page contains DCE 42.
[END]

The condition respects the standard record restrictions and follows the page configured as content source through content_from_pid.

Why DCE ships its own Cache Manager? 

In DCE 2.1 the TYPO3's core cache manager has been used to cache DCE code. But TYPO3 does not allow to use its Cache Manager during bootstrapping (limbo mode) in TYPO3 10 anymore. Therefore DCE provides it's own cache manager.

The shipped cache manager stores generated files below var/cache/code/dce.

When clearing TYPO3's system caches in the backend or with the cache:flush CLI command, the DCE code cache is rebuilt automatically.

When warming an empty cache from the command line, run cache:flush --group system before cache:warmup --group system so the DCE code cache exists before TYPO3 builds its system caches.

Features 

• Slugs for detail pages
• Thanks to Symfony Expression Language, you can use multiple DCE fields as slug
• Field contents used for slug, get sanitized
• Fallback if slugs are not unique (in this case, the uid of content element is appended to slug)

• Modify current page title on detail page

  • based on its own detail-page title expression
  • you can replace, prepend or append the DCE detail page title

Installation 

Once you've upgraded to DCE 2.6, you just need to apply the following routing enhancer configuration in your sites configuration yaml:

routeEnhancers:
  DceWithDetailpage:  # you are free to choose a unique name here
    type: Simple
    routePath: '/show/{detailDceUid}'  # the given argument, must match with set detailpage_identifier
    aspects:
      detailDceUid:  # Same here
        type: PersistedAliasMapper
        tableName: tt_content
        routeFieldName: tx_dce_slug

Now, all DCEs with detail page enabled and identifier set to detailDceUid get beautified slugs.

Configuration 

On tab "Detail page" in every DCE you find three new options:

• Slug expression
• Page title expression
• Use page title expression as page title

How it works 

DCE adds a new column tx_dce_slug to the tt_content table. A non-empty slug expression controls whether DCE generates and stores a slug. The "Enable detail page" option separately controls whether a request can trigger the detail template; disabling it alone does not clear an existing slug.

An after-save-hook updates the slug every time:

• a content element get updated (or created)

• the slug expression in DCE changed

  • then, all content elements existing, based on current DCE, get updated
  • slugs get removed, when slug expression is empty

With this static slug set, the routing enhancer configuration works with standard PersistedAliasMapper.

Tips 

To make the illusion of a detail page perfect, here are some tips for you.

[request.getQueryParams()['detailDceUid'] > 0]
    styles.content.get.select.uidInList {
        data = GP:detailDceUid
        intval = 1
    }
[END]

page.10 < styles.content.get

page.10 =< styles.content.get

[request.getQueryParams()['detailDceUid'] > 0]
    lib.dynamicContent.20.select.uidInList {
         override.cObject = TEXT
         override.cObject.data = GP:detailDceUid
         override.cObject.intval = 1
         override.if {
             value.data = register:colPos
            equals = 0
         }
    }
[END]

plugin.tx_seo.config.xmlSitemap.sitemaps.pages.provider = T3\Dce\Seo\XmlSitemap\DetailPagesXmlSitemapDataProvider

Available variables 

Inside of the DCE view helper you can access the following variables:

• {dce}
• {contentObject}
• {fields} and {field}

Usage 

Everytime you can define a Symfony expression in DCE you have the following variables available:

• dce (object)
• contentObject (array)
• All field variables you have defined

When you have e.g. a field with variable "title", you can simply enter title. Then the value of this field is used.

To concatenate multiple fields you can use the tilde sign (~) like this:

firstName ~ ' ' ~ lastName

When you want to add some custom strings (like the space between firstname and lastname), those have to be wrapped with single or double quotes.

The whole DCE object (dce) and the row of tt_content item (contentObject) are also available:

dce.getTitle() ~ ' ' ~ contentObject['uid']

Helpful Links 

• Symfony Expression Syntax (Docs)

Files root paths 

Since version 2.9 DCE is able to load and use template files from multiple locations, in frontend context. You can check the default configuration in Configuration/TypoScript/setup.typoscript.

Example of setup override:

plugin.tx_dce.view.templateRootPaths.10 = EXT:my_template/Resources/Private/Dce/Templates/
plugin.tx_dce.view.partialRootPaths.10 = EXT:my_template/Resources/Private/Dce/Partials/
plugin.tx_dce.view.layoutRootPaths.10 = EXT:my_template/Resources/Private/Dce/Layouts/

Writing the event listener 

First, you need to create a new event listener class. The following example is located in your custom extension, under the path Classes/EventListener/ModifyConfigurationTemplatesEventListener.php.

This example adds one new snippet group (at the beginning) and adds two field configuration code snippets:

<?php

namespace Vendor\Extension\EventListener;

use T3\Dce\Event\ModifyConfigurationTemplateCodeSnippetsEvent;

class ModifyConfigurationTemplatesEventListener
{
    public function modify(ModifyConfigurationTemplateCodeSnippetsEvent $event): void
    {
        $templates = $event->getTemplates();

        // Adds new group "Custom templates" to the beginning of template array
        $templates = ['My custom templates' => []] + $templates;

        // Adds new example snippet
        $templates['My custom templates']['My first example'] = <<<XML
<config>
    <type>input</type>
    <default>Example</default>
</config>
XML;

        // Adds another example to existing group
        $templates['TYPE: text']['Another example'] = <<<XML
<config>
    <type>text</type>
    <!-- Your custom config goes here -->
</config>
XML;

        // Sets the modified templates array
        $event->setTemplates($templates);
    }
}

Register the event listener 

Next, you need to register the event listener.

Like any other event listener, you can register it in the Configuration/Services.yaml file, inside your extension:

services:
    # ...

    Vendor\Extension\EventListener\ModifyConfigurationTemplatesEventListener:
        tags:
            -   name: event.listener
                identifier: 'dce-modify-configuration-templates-event-listener'
                event: T3\Dce\Event\ModifyConfigurationTemplateCodeSnippetsEvent
                method: 'modify'

Screenshot 

The example above adds these two new code snippets (one in a new group, one in an existing one):

Upgrade from TYPO3 v13 

Update TYPO3 and DCE with Composer. Existing DCE records using the former default wizard group common must be changed to the TYPO3 v14 group default:

UPDATE tx_dce_domain_model_dce SET wizard_category = 'default' WHERE wizard_category = 'common';

The dce:format.cdata ViewHelper has been removed. Replace usages in stored and file-based templates with Fluid's native CDATA syntax:

<![CDATA[
    {{{field.xml}}}
]]>

Then run the TYPO3 database schema update, flush all caches and verify the DCE backend module, existing DCE content elements and frontend output.

Upgrade from TYPO3 v12 

Prepare the installation before updating the TYPO3 core:

1. Update DCE to version 3.3.2 while the installation still runs TYPO3 v12.
2. Add required database columns, but keep obsolete DCE MM tables until the DCE upgrade wizards have finished.
3. Run all DCE and TYPO3 upgrade wizards offered by the Install Tool.
4. Complete the database schema update and flush all caches.
5. Verify that no DCE upgrade wizard is pending and that existing DCE content elements work correctly.
6. Upgrade directly to TYPO3 v14.3 and DCE 4.0, and apply the manual changes described in the section above. From DCE's perspective, an intermediate upgrade to TYPO3 v13 is not required if all upgrade wizards provided by DCE 3.3.2 have been completed while the installation was still running TYPO3 v12.

Older installations 

Do not update a very old TYPO3 installation and DCE to their current versions in a single Composer operation. Create a database and file backup, upgrade TYPO3 one major version at a time and use a matching DCE version at each step. Once the installation runs TYPO3 v12, install DCE 3.3.2 and follow the steps above.

DCE 3.3.2 contains the migrations for legacy field relations, FlexForm sheet identifiers, malformed variable names, old file fields and file references. Do not remove obsolete DCE MM tables before these migrations have finished. Some file field migrations also require manual changes to the affected Fluid templates.

If TYPO3 or DCE has already been upgraded without running these migrations, restore the pre-upgrade backup or use a temporary TYPO3 v12 installation with DCE 3.3.2 and the old database. Current DCE releases can no longer migrate these legacy data structures.

How to access to FAL images? 

You can simply iterate over the variable you have defined for the FAL field. Usage of old FAL view helper is not necessary anymore. But you need to, add these two lines to the field configuration:

<dce_load_schema>1</dce_load_schema>
<dce_get_fal_objects>1</dce_get_fal_objects>

In your Fluid template you can simply use the images like this:

<f:for each="{field.myImages}" as="image" iteration="iterator">
    <f:image image="{image}" />
</f:for>

If you want to output only the first image you can use this one liner:

<f:image image="{field.myImages.0}" />

Related tt_content fields are also resolved for convenient use in Fluid templates:

• {contentObject.media} is resolved as a relation.
• {contentObject.assets} is resolved when Fluid Styled Content is loaded and is the field displayed by DCE's media-tab option.
• {contentObject.categories} is resolved when the field is present.

How to nest DCE content elements? 

In DCE you are able to nest other DCEs. That means you create a child DCE and a parent DCE and assign the children to the parent. To enable the parent DCE to store children you need to add a new field with type "group".

Example field configuration (Variable name: "children"):

<config>
    <type>group</type>
    <allowed>tt_content</allowed>
    <size>5</size>
    <minitems>0</minitems>
    <maxitems>999</maxitems>
    <dce_load_schema>1</dce_load_schema>
</config>

The dce_load_schema flag does the trick here. It realizes, that the tt_content item you have added is a DCE and returns the DCE object itself. For any other content element, which is no DCE, it will return the tt_content row as associative array.

But we assume, that you have just added content elements based on DCEs to the "children" field. In your fluid template you can now do this:

<ul>
    <f:for each="{field.children}" as="childDce" iteration="iterator">
        <li>{childDce.render -> f:format.raw()}</li>
    </f:for>
</ul>

• first we are iterating through all children, using the f:for loop
• then we call and output the render() method of child DCE
• because fluid escapes all html by default, we need to use the f:format.raw view helper

If you do not want to output the whole template of the child DCE, access individual fields through get:

<f:for each="{field.children}" as="childDce" iteration="iterator">
    <li>{childDce.get.myCoolField}</li>
</f:for>

Am I also able to use file collections? 

Since version 0.11.x of DCE you are. Just add a group field, set allowed tablename to "sys_file_collection" and add the dce_load_schema option.

Example field configuration:

<config>
    <type>group</type>
    <allowed>sys_file_collection</allowed>
    <size>5</size>
    <minitems>0</minitems>
    <maxitems>999</maxitems>
    <dce_load_schema>1</dce_load_schema>
</config>

Your Fluid template receives an array of FileCollection models. Both File and FileReference items can be passed directly to the image ViewHelper:

<f:for each="{field.collections}" as="collection">
    <f:for each="{collection.items}" as="item">
        <f:image image="{item}" maxWidth="250" alt="" />
    </f:for>
</f:for>

How to readout an image in a Fluid template and give it a click enlarge function? 

Current DCE file fields provide an array of FAL FileReference objects. To render the first selected image with a link to its processed full-size variant, use:

<f:if condition="{field.yourPicture.0}">
    <a href="{f:uri.image(image: field.yourPicture.0)}" class="your-lightbox-class">
        <f:image image="{field.yourPicture.0}" alt="Thumbnail" maxWidth="100" maxHeight="100" />
    </a>
</f:if>

With the f:image view helper a thumbnail of the image, that should be shown, is issued. TYPO3 creates an image with a reduced size and stores it in fileadmin/_processed_/.

In the href parameter of the link, which should show the big version of the image when it is clicked, you use the f:uri.image view helper. In principle it is the same as the f:image view helper, but instead of an image only a URL is created.

The benefit of using this view helper is that you also can use height and width to limit the size of the big image (e.g. 800x600).

How to apply custom CKeditor configuration in DCE? 

When you've defined a DCE field as RTE (rich text editor), you also defined the "richtextConfiguration" to be used, e.g. "default", "minimal" or something custom.

TYPO3 resolves the RTE preset in this order: field-specific PageTS, the field's richtextConfiguration, the global RTE.default.preset PageTS setting, and finally the default preset. Therefore, a DCE field's richtextConfiguration takes precedence over the global default. Only field-specific PageTS can override it.

How to render the content of an RTE field? 

You have to enclose the RTE field with the format.html view helper to get the HTML tags of the RTE rendered.

<f:format.html>{field.rteField}</f:format.html>

You can also use the inline notation:

{field.rteField -> f:format.html()}

How to access the current TypoScript setup? 

In frontend, you can access directly the TypoScript setup from current page, using {tsSetup.lib.xyz.value}.

How to link to the detail page? 

The link to changeover to the detail page looks like this:

<f:link.page additionalParams="{detailDceUid: contentObject.uid}">Detail</f:link.page>

Where detailDceUid is the value of the field "Detail page identifier (GET parameter)" you have set on the "Detail page" tab.

How to wrap my content elements with a container? 

Sometimes you need a wrapping element in HTML template, for all content elements from same type. I recommend to use EXT:container, because it brings columns to content elements which are structured in database.

You can also use the DCE feature DCE Container, which simulates a container for certain content elements in a row, based on the same DCE.

How to change the long title in content wizard for DCE group 

If you enable DCEs to be visible in content wizard, they can be grouped in a new group, introduced by DCE, called "Dynamic Content Elements". This can be too much text in some cases.

If you want to rename this group just use this code in PageTS:

mod.wizards.newContentElement.wizardItems.dce.header = Whatever you want

You can also modify the position of the group, in PageTS. This is the default value:

mod.wizards.newContentElement.wizardItems.dce.after = default

4.0.0 

First release with added TYPO3 v14 support

• [FEATURE][!!!] Add TYPO3 v14.3 support and drop support for TYPO3 v13 and v12
• [FEATURE] Revive syntax highlighting by integrating the TYPO3 code editor
• [FEATURE] Add {contentElementRecord} as available variable in Fluid templates
• [TASK] Render DCE containers separately in the Visual Editor
• [TASK] Migrate rendering, records, ViewHelpers, PageTSconfig and DataHandler usage to current TYPO3 APIs
• [TASK] Remove legacy upgrade wizards, deprecated DCE APIs and obsolete configuration options
• [TASK] Improve and update the documentation and screenshots
• [BUGFIX] Prevent recursive DataHandler updates
• [BUGFIX] Rebuild the DCE cache on CLI cache flush
• [BUGFIX] Fix DCE relation imports and handling of empty FlexForm sections
• [BUGFIX] Register custom DCE icons after TYPO3 has booted
• [TASK] Fix Install Tool DI container compatibility (Thanks to Thomas Ainhauser)
• [BUGFIX] Fix FlexForm and FAL collapse handling (Thanks to Thomas Ainhauser)
• [BUGFIX] Improve backend preview and field labels (Thanks to Thomas Ainhauser)

3.3.2 

• [BUGFIX] Revert accidentally added changes

3.3.1 

• [TASK] Update copyrights
• [BUGFIX] Force type to XML (Thanks to Georg Ringer)
• [BUGFIX] Fix exception when pi_flexform is null in database (Thanks to Stefan Hilhorst)
• [FEATURE] Add support for EXT:vici tables

3.3.0 

• [FEATURE] Add {site} to variables passed to DCE templates in frontend
• [TASK] Fix ES6 configuration for DCE javascript

3.2.7 

• [BUGFIX] Fix "dce_enable_autotranslation" functionality
• [BUGFIX] Do not use RestrictionContainers in database queries in content element generator

3.2.6 

• [BUGFIX] Fix list view search for DCE elements to respect selected depth (Thanks to Markus Gerdes)

3.2.5 

• [TASK] Apply code-style fixes
• [DEVOPS] Add code quality checks
• [BUGFIX] Fix PageTitleProvider in v13
• [BUGFIX] Fix missing global TypoScript in v13
• [TASK] Update copyrights
• [BUGFIX] Fix FalViewHelper for TYPO3 v13 (Thanks to Martin Kutschker)
• [BUGFIX] Fix negated query in FixMalformedDceFieldVariableNamesUpdateWizard
• [BUGFIX] Use UpgradeWizard annotation to register wizards
• [DEVOPS] Set b13/container to version ^3.0
• [DEVOPS] Enable deprecation log in DDEV environment

3.2.4 

• [BUGFIX] Add check for admin privileges, before showing "Edit DCE" button in content element
• [BUGFIX] Respect field type when checking for section fields

3.2.3 

• [FEATURE] Add dark mode support
• [BUGFIX] Avoid Fluid rendering issues with disabled Jit compiler (Thanks to Florian Rival)

3.2.2 

• [BUGFIX] Render label for custom DceCodeMirrorFieldRenderType
• [TASK] Add additional classes in DceModule, to ensure styling of badges
• [BUGFIX] Fix exceptions in DceFieldLabel
• [BUGFIX] Fix missing templateFileName in DceModuleController
• [BUGFIX] Fix dcefield TCA to reapply display conditions
• [BUGFIX] Backend Problem with Powermail Forms (Thanks to Sebastian Fahrenkrog)
• [TASK]Improve convertUidToCType for DCEs with identifier (Thanks to Luis Becker)
• [TASK] Clean up TCA (Thanks to Nikita Hovratov)

3.2.1 

• [BUGFIX] Do not cause PHP warning in custom TtContentLabel user function

3.2.0 

First release with added TYPO3 v13 support

• [TASK] Improve labels and styling in DCE backend module
• [TASK] Fix DCE group position in new content element wizard
• [BUGFIX] Always enable Direct Output for DCEs with enabled container
• [BUGFIX] Register DCE custom icons also when the DCE is disabled
• [TASK] Remove "Disables the "div.csc-default" wrapping" option in DCE
• [TASK] Remove "Prevent header copy suffix" option in DCE
• [TASK] Remove third parameter in DataHandler's recordInfo method calls
• [TASK] Make font weight in code editor bold
• [TASK] Change the way to ask Doctrine for the type name of a column
• [TASK] Replace all occurrences of PDO column types
• [TASK] Fix declaration of DceModuleController's initializeAction
• [TASK] Raise TYPO3 requirement to include v13
• [DEVOPS] Fix site hostname in v13 install script

3.1.4 

• [TASK] Move CodeEditor.css contents as inline styles
• [BUGFIX] Fix TtContentLabel array handling in Workspace mode
• [BUGFIX] Update sys_file_reference table for hidden element (Thanks to Florian Rival)
• [BUGFIX] Fix "Edit DCE" appearing on any content element
• [DEVOPS] Upgrade DDEV configuration
• [BUGFIX] Add a check for existence of $GLOBALS['TYPO3_REQUEST'] (Thanks to Florian Rival)
• [BUGFIX] Fix bug in filewizard (Thanks to Thomas Wittich)

3.1.3 

• [TASK] Update copyrights
• [TASK] Add "softref" configuration to RTE field code snippet
• [BUGFIX] Fix usage of $parameters['row']['enable_container'] in ItemsProcFunc
• [BUGFIX] Fix usage of $GLOBALS['TYPO3_REQUEST']
• [BUGFIX] Fix icon color of btn-primary in backend module
• [DOCS] Fix syntax for reference (Thanks to Sybille Peters)
• [BUGFIX] Fix TtContentLabel userfunction in case of incomplete data (Thanks to Sybille Peters)

3.1.2 

• [BUGFIX] Return early in TtContentLabel when special case "new" (Thanks to Nikita Hovratov)

3.1.1 

• [BUGFIX] Provide JavaScript module "@t3/dce/code-editor" in FormEngine page init

3.1.0 

• [BUGFIX] Fix adjusting height when in inserting code and disable spellcheck
• [FEATURE] Add ModifyConfigurationTemplateCodeSnippetsEvent
• [BUGFIX] Removed unused $isIn parameter in custom field validators
• [TASK] Refactor DCE's TypoScript utility
• [TASK] Add migration for type file allowed config (Thanks to Nikita Hovratov)
• [BUGFIX] Do not pass null value to linkEditContent method, in DcePreviewRenderer

3.0.2 

• [BUGFIX] Fix DCE icon in backend module
• [BUGFIX] Allow DCE in legacy installations
• [BUGFIX] Restore section fields in Simple backend view

3.0.1 

• [TASK] Provide upgrade wizard for FlexForm sys_file_references
• [TASK] Remove MigrateOldNamespacesInFluidTemplateUpdateWizard

3.0.0 

First release with TYPO3 v12 support

• Added TYPO3 12.4 LTS support
• Dropped v10 and v11 support
• Applied Massive refactorings

Checkout Upgrading DCE section

Thanks to Stephan Bauer for testing and supporting.

2.9.5 

• [TASK] Update copyrights
• [BUGFIX] Remove "useCacheHash" from link.typoscript code snippet
• [TASK] Assign "data" variable to Fluid template as alias for "contentObject"
• [BUGFIX] Fix disabling of DCE cache
• [BUGFIX] Remove wrong php requirements in ext_emconf.php
• [DEVOPS] Upgrade DDEV configuration

2.9.4 

• [BUGFIX] Fix PHP 8.1 issues in File to Fal Update Wizard (thanks to Peter Kraume)
• [BUGFIX] Fix PHP 8.1 issue in label_userFunc (thanks to Peter Kraume)
• [BUGFIX] Fix non-existing array keys warnings
• [BUGFIX] Fix deprecated usage of ${var}
• [TASK] Fix warnings in backend (thanks to Georg Ringer)

2.9.3 

• [BUGFIX] Fix undefined array keys (for PHP 8)
• [BUGFIX] Do not try to migrate DCEs without valid UID

2.9.2 

• [BUGFIX] Respect hidden DCEs in FileToFalUpdateWizard
• [DOCS] Improve docs
• [BUGFIX] Respect content element's language when checking for unique slug
• [BUGFIX] Respect current language in DetailPagesXmlSitemapDataProvider
• [BUGFIX] Fix PHP warning in FalViewHelper

2.9.1 

• [BUGFIX] Do not show File2FAL update wizard, when no elements to migrate found
• [BUGFIX] Do not use deprecated ResourceFactory::getInstance() method in File2Fal wizard
• [BUGFIX] Do not throw warnings when EXT:container is installed

2.9.0 

• [DOCS] Thanks to the feature sponsor Silverback
• [BUGFIX] Avoid php warning in TtContentLabel, when being used in Recycler module
• [BUGFIX] Fix PHP 8.0 warnings in DceRepository
• [BUGFIX] Use Compatibility layer to get FQCN of PageRepository
• [BUGFIX] Use old Doctrine query builder syntax in DetailPagesXmlSitemapDataProvider
• [TASK] Update links in DCE module help menu
• [FEATURE] Added ability to use TypoScript to configure Fluid root file paths (partials & layouts) Thanks to Romain Tiger for contributing this feature!
• [FEATURE] Add "dce_skip_translation" field option
• [BUGFIX] Provide LiveSearch XClass for older TYPO3 version (9&10)
• [FEATURE] Add XML sitemap data provider for DCEs with detailpage enabled
• [BUGFIX] Fix migration of section fields in File2FAL Update wizard
• [FEATURE] File to FAL update wizard
• [BUGFIX] Fix link analyser for DCEs
• [BUGFIX] Do not treat texts with spaces as link (in LinkAnalyserSlot)
• [BUGFIX] Fix undefined array keys in DceRepository (for PHP 8)
• [BUGFIX] Fix undefined array key in FalViewHelper (for PHP 8)

2.8.4 

• [BUGFIX] Remove replace for "typo3-ter/dce" in composer.json (Daniel Haupt)
• [BUGFIX] Prevent undefined array key warning in AfterSaveHook (creationell)

2.8.3 

• [BUGFIX] Add missing slash when resolving t3:// links
• [TASK] Simplify ext_emconf

2.8.2 

• [DEPRECATION] Mark "file:" and "t3://" as template path deprecated
• [BUGFIX] Do not use deprecated method in FileInfoViewHelper
• [BUGFIX] Prepend Environment::getPublicPath() to resolved t3://file links
• [BUGFIX] Do not apply langauge overlay, when in free mode
• [BUGFIX] TCA output flexform (thanks to Sebastian Iffland)

2.8.1 

10th Anniversary of the DCE extension for TYPO3 🎉 2012-2022

• [TASK] Update copyright
• [TASK] Prevent exception in backend module, when a DCE has no custom icon set
• [TASK] Remove file picker wizard (inputLink) for DCE template paths
• [BUGFIX] Apply language overlay to translated container elements
• [BUGFIX] Remove unused extension configuration in AfterSaveHook
• [BUGFIX] Fix PHP warning, when accessing non existing array key (PHP 8 support)

2.8.0 

This version has been sponsored by web-crossing GmbH.

• [FEATURE] Support DCE container within EXT:news detail view
• [DOCS] Remove invalid links to forge.typo3.org
• [BUGFIX] Remove unnecessary extend of AbstractCondition

2.7.7 

• [TASK] Replace ResourceFactory::getInstance() calls
• [BUGFIX] Use DBAL expressions in update wizards
• [BUGFIX] Use ObjectManager when creating new Extbase repository instance
• [BUGFIX] Fix escaping of WrapWithCurlyBracesViewHelper

2.7.6 

• [BUGFIX] Fix DceCodeMirrorFieldRenderType declaration

2.7.5 

• [BUGFIX] Fix accidentally added namespace import when creating DCE cache
• [TASK] Use DceRepository instance for extracting uid from CType

2.7.4 

• [BUGFIX] Fix usage of iconGroups in tt_content's CType configuration
• [DEVOPS] Update php-cs-fixer and phpstan
• [CLEANUP] Indention fixes
• [TASK] Make DCE's CacheManager non-singleton
• [TASK] Use correct file permissions when creating cache folder

2.7.3 

• [BUGFIX] Remove usage of $_EXTKEY
• [TASK] Cleanup ext_tables.sql
• [TASK] Remove "starttime" and "endtime" from DCE's TCA
• [DOC] Improve README
• [DOC] Add Gridelements notice (resolveChildFlexFormData)

2.7.2 

• [DEVOPS] Fixing code style issues
• [BUGFIX] Do not perform file_exists after unlinking (deleting) cache file
• [BUGFIX] Do not clear DCE caches everytime any TYPO3 cache gets cleared
• [BUGFIX] Fix typehinting for updateTcaMappingsAction in DceModuleController

2.7.1 

• Security related bugfix release

2.7.0 

• [BUGFIX] Remove unused language fields and fix copying/duplicating DCEs on root level
• [FEATURE] Symfony expressions for Simple Backend View header
• [BUGFIX] Fix non-rendered container items, when content elements get rendered multiple times
• [BUGFIX] Update outdated color picker config
• [DEVOPS] Update DDEV environment and add project environment with Composer
• [TASK] Add required "extra.typo3/cms.extension-key" value
• [FEATURE] TYPO3 11 Compatibility (dropped TYPO3 8 support)

2.6.2 

• Security related bugfix release

2.6.1 

• [BUGFIX] Add missing "classmap" argument in ext_emconf autoload section
• [FEATURE] Add support for EXT:container
• [BUGFIX] Only add FrontendRestrictionContainer when TYPO3_MODE equals "FE"

2.6.0 

• [TASK] Update module icons and header
• [TASK] Extend .gitignore
• [DEVOPS] Apply fix for DDEV 1.15
• [FEATURE] Add DceViewHelper
• [FEATURE] Add dedicated "detailpage_title_expression" field for detailpage title generation
• [TASK] Code style
• [TASK] Show "Detail page" as badge in DCE module, when enabled
• [BUGFIX] Do not show new slug settings in TYPO3 8
• [TASK] Add documentation for new slug features
• [FEATURE] Add "use slug as title" DCE option and provide new PageTitleProvider
• [FEATURE] Slugs for detail pages
• [BUGFIX] Register old "PageLayoutViewDrawItemHook" when EXT:gridelements is active

Thanks to Silverback (https://silverback.st/) for sponsoring this release!

2.5.2 

• [BUGFIX] Use old PageLayoutViewDrawItemHook when "fluidBasedPageModule" is disabled in TYPO3 10
• [TASK] Apply FrontendRestrictionContainer to QueryBuilder in ContainerFactory
• [BUGFIX] Fix DCE container when content-fallback takes effect
• [BUGFIX] Remove deprecated $string{0} syntax from DceRepository

2.5.1 

• [TASK] Improve ContainerFactory
• [DEVOPS] Add DDEV Environment
• [BUGFIX] Do not use Extbase Controller Action to return DCE Instance
• [BUGFIX] Add mandatory renderType
• [BUGFIX] Change configuration position fpr palettes and language-path
• [TASK] Register LinkAnalyserSlot as EventListener in TYPO3 10
• [TASK] Use new PreviewRenderer in v10 for backend templates

2.5.0 

• [TASK] Improve MigrateDceFieldDatabaseRelationTrait
• [BUGFIX] Fix exception when using Postgtres
• [TASK] Small documentation improvements
• [BUGFIX] Keep page cache-able, when using DCE containers, in TYPO3 8
• [BUGFIX] Fix multiple entries of the same category in {contentObject.categories}
• [TASK] Code style fixes
• [DEVOPS] Fix broken code quality check pipeline
• [BUGFIX] Prevent Linkanalyzer to check non DCE records
• [BUGFIX] Make CacheManager respect fileCreateMask
• [TASK] Refactor "File Abstraction Layer" code snippets
• [BUGFIX] Codemirror fix for TYPO3 10
• [BUGFIX] Available templates switcher cuts of .xml instead of wrong .xlf
• [BUGFIX] Only apply "Prevent header copy suffix" when status is "new" in after save hook
• [TASK] Use new UpdateWizards also in TYPO3 9
• [BUGFIX] Fix instantiating of ObjectManager
• [TASK] Provide UpdateWizards, based on old Updates

2.4.1 

• [BUGFIX] Fix wrong version constraints

2.4.0 

• [FEATURE] TYPO3 10 Compatibility

2.3.1 

• [BUGFIX][!!!] Fix queries which build content elements
• [BUGFIX] Do not throw exceptions in Content Element Generator

2.3.0 

• [FEATURE] Add new option "container_detail_autohide"
• [BUGFIX] Fix Doctrine DBAL queries with empty field where clauses

2.2.1 

• [BUGFIX] Fix wrong escaping of quotes, in OutputPlugin Generator
• [TASK] Improve error message, when a DCE Field has a mapping to a non-existing tt_content column
• [TASK] Use Doctrine API to get list of table and column names
• [TASK] Make DCE work, even without fluid_styled_content installed
• [TASK] Add hint to documentation, that tab DCE fields changes the FlexForm structure
• [TASK] Improve README.md
• [BUGFIX] Fix hidden DCE container items

2.2.0 

• [FEATURE] New "Prevent header copy suffix" DCE option
• [BUGFIX] Fix deprecated clear-cache call
• [BUGFIX] Do not use "module-help" icon in DCE backend module
• [FEATURE][!!!] Remove old TYPO3_DB calls with Doctrine DBAL
• [FEATURE] Make mapped "tx_dce_index" contents searchable in backend
• [TASK] Improve and document Code Caching feature
• [BUGFIX] Use heredoc for generated FlexForm XML
• [BUGFIX] Fix missing FQCN in generated PHP code
• [FEATURE] Implement own CacheManager

2.1.0 

• [TASK] Use native database connection, when existing
• [FEATURE][!!!] Re-implement Caching of generated PHP code
• [TASK] Improve code snippets
• [BUGFIX][!!!] Make access field values of child DCEs work in TYPO3 9 (before: {dce.fieldName}, now: {dce.get.fieldName})
• [BUGFIX] Fix localizedUid conditions in FalViewHelper

2.0.6 

• [BUGFIX] Do not throw exception in backend when proper flexform missing
• [FEATURE] Improve tx_dce_dce behaviour
• [BUGFIX] Remove unused code which causes errors

2.0.5 

• [BUGFIX] Allow lowercase only for DCE identifier
• [BUGFIX] Include tx_gridelements_columns in db query (thanks to Matthias Bernad)

2.0.4 

• [BUGFIX] Do not display "Edit DCE" button for all content elements

2.0.3 

• [BUGFIX] Add default value for tx_dce_dce column in tt_content table
• [BUGFIX][!!!] Do not use hidden DCE fields

2.0.2 

• [TASK] Add "Upgrading DCE" to documentation
• [BUGFIX] Allow null value for input in LanguageService::sL
• [BUGFIX] Fix resolving of non-dce tt_content records

2.0.1 

• [BUGFIX] Check for correct table when resolving related records

2.0.0 

• Change package name and namespace to t3/dce and \T3\Dce
• Add identifier to DCE, which allows to control the CType of the content element
• Added direct_output mode
• Fixed behaviour of detail pages
• Global namespace registration for dce: in Fluid templates
• Allow partials and layouts fallback
• Add {$variable} to field configuration (used for FAL)
• Add csh-description for all fields
• Refactored user conditions (Symfony expression language)
• Removed update check functionality
• Removed all extension manager settings
• Refactored and cleaned up code base
• New FlexForm rendering (using DomDocument instead of FluidTemplate)
• DCE is 100% deprecation notice free in TYPO3 9.5 LTS
• Add complete documentation (!)

1.6.0 

• Added TYPO3 9.5 LTS and dropped TYPO3 7.6 LTS support

1.5.x 

• Completely refactored code injection (for TCA).

  Instead of requiring a dynamic generated php file, the code is dynamically executed, at the points where TYPO3 expects it.

  So all cache clear functionality and options has been removed.

  If you want to make new DCEs visible you need to clear the system cache or disable the cache at all, like you need to do when modifying the TCA manually.

  DCE should behave exactly the same like before, just without need of cache files in typo3temp.

• Major bugfixes and improvements (DceContainer & SimpleBackendView)
• Removed f:layout in DCE templates, by default
• Applied refactorings

1.4.x 

• DCE major release with many new features and improvements
• One breaking change, regarding backend templates.
• Check out release slides for all new stuff: http://bit.ly/2SFbIzC
• Bug and compatibility fixes for TYPO3 8.6
• More fixes for TYPO3 7/8 compatibility in backend.
• Bug and compatibility fixes for TYPO3 8
• Also improved dev-ops tools.
• The typolink view helpers in DCE are marked as deprecated. Please use f:link.typolink or f:uri.typolink instead.
• Compatibility fixes for TYPO3 7.6 and 8.7 LTS. Also updated RTE code snippets.
• Fixed Typolink view helper for TYPO3 7.6 LTS and added conditional code snippets (for 7.6 and 8.7 snippets) in DCE configuration.
• Fixes big performance issue in backend and increases compatibility to EXT:flux.
• Massive refactorings, to improve speed of DCE extension. Special thanks to Bernhard Kraft!
• Small bugfix and add example to code snippets of RTE, of how to define a preset for CKeditor.
• Permission issue for non-admins fixed
• Removed php warnings in backend
• Fixed Typolink 8.7 code snippet

Open tasks 

See all open tasks here in the Github issue tracker.

Facebook page 

To connect the DCE users together and have a central place of announcements, DCE got its own Facebook page, now.

Join it: https://www.facebook.com/TYPO3.DCE.Extension

Slack channel 

Also you can join the #ext-dce Slack channel on typo3.slack.com.

Donate 

If you like the dce extension, feel free to donate some funds to support further development.

Contribute 

If you are a developer and you want to submit improvements as code, you can fork https://github.com/a-r-m-i-n/dce and make a pull request to DCE's v14 branch.

Thanks!