Bug #89529
closedEXT:form: value in singleselect contains dot/period AT END - rendering fails
0%
Description
Hi there seems similar to those and therefor should be fixed in 8.7 already:
https://forge.typo3.org/projects/typo3cms-core/repository/revisions/b4b32de503ef0eb4df520dc0cf41f0fd84376bb3
But perhaps it was not tested if the period/dot is at the end of the value.
Form building is possible in the backend gui but rendering in frontend fails with:
frontend error: Oops, an error occurred! Argument 1 passed to TYPO3\CMS\Form\Mvc\Configuration\TypoScriptService::resolveTypoScriptConfiguration() must be of the type array, string given, called in /var/www/xxxx/vendor/typo3/cms/typo3/sysext/form/Classes/Mvc/Configuration/TypoScriptService.php on line 85 backend log: Core: Exception handler (WEB): Uncaught TYPO3 Exception: Argument 1 passed to TYPO3\CMS\Form\Mvc\Configuration\TypoScriptService::resolveTypoScriptConfiguration() must be of the type array, string given, called in /var/www/xxxx/vendor/typo3/cms/typo3/sysext/form/Classes/Mvc/Configuration/TypoScriptService.php on line 85 | TypeError thrown in file /var/www/xxxx/vendor/typo3/cms/typo3/sysext/form/Classes/Mvc/Configuration/TypoScriptService.php in line 74. Requested URL: https://www.xxx/x/anmeldeformular/?no_cache=1
FAILS:
label value Prof. Dr. Prof. Dr.
WORKS if last period is left out:
label value Prof. Dr. Prof. Dr
T3 v8.7.28 on php 7.0 and 7.3
Files
Updated by Mathias Brodala almost 5 years ago
- File 2019-11-22_13-44.png 2019-11-22_13-44.png added
- Status changed from New to Needs Feedback
I am unable to reproduce the issue with the latest master using the following form definition:
renderingOptions:
submitButtonLabel: Submit
type: Form
identifier: forge89529SelectOptionsWithDotinValue
label: 'Forge 89529: Select Options With Dot in Value'
prototypeName: standard
renderables:
-
renderingOptions:
previousButtonLabel: 'Previous step'
nextButtonLabel: 'Next step'
type: Page
identifier: page-1
label: Step
renderables:
-
properties:
options:
'Prof. Dr.': 'Prof. Dr.'
type: SingleSelect
identifier: singleselect-1
label: 'Single select'
The form field renders just fine in the frontend:
Can you also check with the latest master and attach your form definition if necessary?
Updated by Ingo Müller almost 5 years ago
I'm very sorry but I can't reproduce it on T3 v8.7.29 - so see it as fixed
Updated by Björn Jacob almost 5 years ago
- Status changed from Needs Feedback to Closed
Thank you for your feedback. Closing this issue.