Project

General

Profile

Actions

Bug #85940

closed

Form throws unhelpful exception if a YAML file could not be found

Added by Daniel Goerz over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Could have
Assignee:
Category:
Form Framework
Target version:
-
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:

  1. Include any form definition
  2. Rename the file
  3. The Form Content Element in the Backend shows 'The file "..." does not exist.' That's fine.
  4. 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.


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Task #85357: Show speaking exception message in frontend if form definition is invalidClosedRalf Zimmermann2018-06-23

Actions
Actions

Also available in: Atom PDF