Project

General

Profile

Actions

Bug #24372

closed

Flexform inputfields remain empty regardless of value

Added by Frenck Lutke almost 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2010-12-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Upgrading from TYPO3 4.4.4 results in flexform input fields being displayed empty. The hidden REAL input field does have its value however, as viewed in the source or wherever the value has an effect. The values really are stored, they're just not being displayed in the flexform after saving. At the same time, onchange=reload no longer works.

A quick debug reveals a JavaScript error to be the culprit.

typo3/jsfunc.tbe_editor.js received the following addition since 4.4.4, on line 198:

// Check if we are within a deleted inline element
var testNode = $(form.parentNode);
while(testNode) {
if (testNode.hasClassName && testNode.hasClassName('inlineIsDeletedRecord')) {
return result;
}
testNode = $(testNode.parentNode);
}

Because form is sometimes null, the newly added code causes the script to halt in a lot of flexform configurations. So among other things, typo3form.fieldSet() will not be applied.

SOLUTION: =========
Below the newly added code we find the following check:

if (form) {

The issue is resolved by including the newly added code BELOW this line rather than ABOVE it.
(issue imported from #M16788)


Files

16788.patch (1.07 KB) 16788.patch Administrator Admin, 2011-01-25 10:51

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #24482: FCE with sections loses data in backendClosed2011-01-05

Actions
Related to TYPO3 Core - Bug #21991: Deleted combo records are still validated by TBE_EDITORClosedSusanne Moog2010-01-19

Actions
Actions #1

Updated by Frenck Lutke almost 14 years ago

Sorry, I'm currently not able to create a patch.

Actions #2

Updated by Andreas Kießling almost 14 years ago

I will submit this to core list, this error is also present in 4.5

Actions #3

Updated by Frenck Lutke almost 14 years ago

Confirmed its presence in 4.5. Thanks for submitting a patch, Andreas.

Actions #4

Updated by Steffen Kamper over 13 years ago

committed to svn
4_4 rev 10630
4_5 rev 10631
trunk rev 10632

Actions #5

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF