Project

General

Profile

Actions

Bug #98055

closed

prototypeName defined in form yaml does not have an effect any more

Added by Helmut Hummel over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2022-07-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

With 11.5.13 setting the prototypeName in a form definition has not effect any more.

Prerequisite
When setting this in a form definition:

type: Form
identifier: foo
label: 'Foo form'
prototypeName: fooPrototype

Expectation
I would expect to have the prototype "fooPrototype" to be selected when rendering the form
and no other prototype has been passed.

Actual result:
What actually happens is, that the "standard" prototype is selected.

Analysis

This is due to the new FormRequestHandler class, which already sets the prototype to standard,
if it is not passed into the view helper, instead of allowing it to be null until the form definition is loaded


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #98023: custom prototypes cannot be appliedClosedRalf Zimmermann

Actions
Actions

Also available in: Atom PDF