Bug #77312

Flexform is not rendered in content elements, when list_type is not empty

Added by Armin Vieweg almost 3 years ago. Updated over 1 year ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2016-07-29
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When you have custom content elements using flexform (DCE in this case), which were plugins before, the list_type property may not be empty. In this case the flexform is not rendered properly anymore. Instead you get this:

You can simply reconstruct this issue, by adding any value to list_type property of a content element and edit the item. Of course the content element needs to use pi_flexform.

This issue appears in TYPO3 7.6 and 6.2, so it's not a "new form engine" issue only.

2016-07-29_1704.png View (23.1 KB) Armin Vieweg, 2016-07-29 17:11


Related issues

Related to TYPO3 Core - Bug #79427: Non-plugin content elements not accessible when list_type not empty New 2017-01-23
Duplicated by Dynamic Content Elements (DCE) - Bug #77308: DB field "list_type" breaks rendering of DCE fields in backend Closed 2016-07-29

History

#1 Updated by Riccardo De Contardi over 1 year ago

Does this still happens with TYPO3 8.7? Could it be related to the behavior of the field pi_flexform, which does not get cleaned when you switch from one content element to another (the new xml will be appended)?

#2 Updated by Armin Vieweg over 1 year ago

  • TYPO3 Version changed from 7 to 8

Yes it does. Same behaviour as described before. Tested with 8.7.9.

#3 Updated by Susanne Moog over 1 year ago

  • Category set to FormEngine aka TCEforms

Also available in: Atom PDF