Project

General

Profile

Actions

Bug #84698

closed

Severity for ext:form was not accepted

Added by Stefan Froemken about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2018-04-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:

Description

Hello Core-Team,

I have following yaml configuration for EXT:form:

...
finishers:
  -
    options:
      messageTitle: 'Argh'
      messageBody: 'I am sitting in the %s'
      messageArguments:
        - foo: 'bar'
      severity: -1
    identifier: FlashMessage
...

This will result in following error message:

Argument 1 passed to TYPO3\CMS\Core\Messaging\AbstractMessage::setSeverity() must be of the type integer, string given, called in /Users/stefan/htdocs/typo3_src/typo3/sysext/core/Classes/Messaging/FlashMessage.php on line 42

I have defined that value as int and it is still int while calling FlashMessageFinisher, but there is no early return for options of type int, so severity lands in your preg_replace_callback(whatever) and will be returned as string, which, of cause, is not valid.

Stefan


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #83477: Form finisher parseOption fails with MultiCheckbox / MultiSelectClosedRonald Kools2018-01-04

Actions
Actions

Also available in: Atom PDF