Project

General

Profile

Actions
Copy link

Bug #70610

closed

PropertyMapper directly throws TargetNotFoundException

Added by Mathias Brodala over 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2015-10-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Since TYPO3 6.2.15 the PropertyMapper directly throws a TYPO3\CMS\Extbase\Property\Exception\TargetNotFoundException if thrown by a type converter instead of encapsulating it once with a general TYPO3\CMS\Extbase\Property\Exception just like before.

This is a change in behavior and affects all code which relied on the previous structure to trigger e.g. the regular pageNotFoundHandling of TYPO3.

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #55861: New PropertyMapper must accept not found argumentsClosed2014-02-11

Actions
Actions
Copy link

Also available in: Atom PDF