Bug #82096
openError when adding an inline element inside the FlexForm area of an inline element
0%
Description
It is not possible to add an element of type inline
inside an element of type inline
in the page view.
An "error 500" message is showing up. The logge error message is:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1446996319: Configuration retrieved from FlexForm is incomplete or not of type "inline". | UnexpectedValueException thrown in file /var/www/html/typo3_src-7.6.21-bi/typo3/sysext/backend/Classes/Controller/FormInlineAjaxController.php in line 912.
The same error occurs while trying to expand a collapsed inline element inside an other inline element.
The error is only present in the page view. If I edit the "upper" inline element in list view, there is no error.
It's the same problem described in #71436 and the patch in https://forge.typo3.org/issues/71436#note-49 works when manually applied (see comment of Bart Lammers).
Update: See the working patch in comment #7
More detailed description to reproduce the error:
There is a plugin where I can add elements of type "inline" (in backend). These elements are the parent elements and contain a FlexForm definition. In that FlexForm area I can add some child elements (also of type "inline").
So when I edit my plugin and add some parent element and I try to add a child element, the error occurs. If I save my plugin (with the added parent element) and change to the list view, I am able to edit the parent element directly and add a child element.
The error did not exists in TYPO3 6.2.
Files
Updated by Markus Zipfel about 7 years ago
- Subject changed from Error when adding an inline element inside an inline element to Error when adding an inline element inside the FlexForm area of an inline element
- Description updated (diff)
Updated by Markus Zipfel about 7 years ago
- Related to Bug #71436: Inline in flex with multiple DS fails added
Updated by Wouter Wolters about 7 years ago
- Assignee deleted (
Morton Jonuschat)
Please do not assign issue to anyone!
Updated by Markus Zipfel about 7 years ago
Wouter Wolters wrote:
Please do not assign issue to anyone!
Oh, sorry, Morton was entered as assignee in the linked issue (#71436), so I thought it's a good idea to make sure he knows this one, too.
Updated by Bart Lammers about 7 years ago
In 7.6.22 this problem still persists. Due to changes in the FormInlineAjaxController the patch from Leonie Philine Bitto (https://forge.typo3.org/issues/71436#note-49) does not apply anymore, but the changes still work when manually applied.
Updated by Bart Lammers about 7 years ago
Patch of the same change, but applies to 7.6.22
Updated by Markus Zipfel about 7 years ago
- Priority changed from Should have to Must have
Updated by Sybille Peters over 6 years ago
Thank you for your report.
Even though it has been some time, would you consider checking if your patch idea is still up to date and upload it to our Gerrit review server?
Someone could do this for you, but I am thinking you might like the opportunity to contribute to TYPO3 yourself.
You can find a description of the TYPO3 contribution workflow here: https://docs.typo3.org/typo3cms/ContributionWorkflowGuide/
Hint: If you get stuck anywhere, ask on Slack in the #typo3-cms-coredev channel. You can register in the TYPO3 slack workspace here: https://forger.typo3.com/slack
Thank you in advance!
Updated by Nikolas Hagelstein over 5 years ago
Any news on this issue?.
Cheers,
Nikolas