Actions
Bug #85940
closed
Form throws unhelpful exception if a YAML file could not be found
Start date:
2018-08-23
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:
Description
Steps to reproduce:
- Include any form definition
- Rename the file
- The Form Content Element in the Backend shows 'The file "..." does not exist.' That's fine.
- The frontend however shows the exception "The options "invalid" were not allowed (allowed were: "rendererClassName, renderingOptions, finishers, formEditor, label")"
This Exception is not helpful at all.
We could throw an Exception with a meaningful message instead before the validation of the allowed array keys.
This is just a suggestion. If this was done on purpose (for example to not disclose the path to the file on the server) its fine as it is.
Updated by Wouter Wolters over 5 years ago
- Subject changed from Form throughs unhelpful exception if a YAML file could not be found to Form throws unhelpful exception if a YAML file could not be found
Updated by Gerrit Code Review over 5 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58000
Updated by Daniel Goerz over 5 years ago
- Status changed from Under Review to Closed
Was already fixed three weeks ago ... =)
Updated by Stephan Großberndt over 5 years ago
- Is duplicate of Task #85357: Show speaking exception message in frontend if form definition is invalid added
Actions