Actions
Bug #98077
closedFormEditor display "undefined" for element types
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2022-08-05
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Since version 10.4.29 the form editor display undefined
for the element types.
The change from [SECURITY] Ensure text preview of multivalue items in form editor introduced these behaviour.
The information about the type
is not available within the form element definition.
These affect only TYPO3 10. In TYPO3 11 the @label is used here. https://github.com/TYPO3/typo3/commit/c36447f2f4d719564993cfabe18f7fbeb565b9b3
Patch:
Index: typo3/sysext/form/Resources/Public/JavaScript/Backend/FormEditor/StageComponent.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/typo3/sysext/form/Resources/Public/JavaScript/Backend/FormEditor/StageComponent.js b/typo3/sysext/form/Resources/Public/JavaScript/Backend/FormEditor/StageComponent.js
--- a/Resources/Public/JavaScript/Backend/FormEditor/StageComponent.js
+++ b/Resources/Public/JavaScript/Backend/FormEditor/StageComponent.js (date 1659683036247)
@@ -923,7 +923,7 @@
getHelper()
.getTemplatePropertyDomElement('_type', template)
- .append(document.createTextNode(getFormElementDefinition(formElement, 'type')));
+ .append(document.createTextNode(formElement.get('type')));
getHelper()
.getTemplatePropertyDomElement('_identifier', template)
.append(document.createTextNode(formElement.get('identifier')));
Files
Updated by Andreas Kienast over 2 years ago
- Sprint Focus set to On Location Sprint
Updated by Oliver Hader about 2 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Riccardo De Contardi over 1 year ago
- Related to Bug #98389: Text “undefined” when hovering over a field in the editor since update to TYPO3 10 added
Updated by Riccardo De Contardi over 1 year ago
I guess this is the same issue: #98389
Updated by Riccardo De Contardi over 1 year ago
- Status changed from New to Closed
I close this issue as it affects version 10 but not 11 and 12 (see also #98389) ; if you think that this is the wrong decision or experience the issue again on recent TYPO3 versions, please reopen it or open a new issue with a reference to this one.
Thank you
Actions