Feature #55869

Allow custom handling of propertyMapping errors

Added by Georg Ringer over 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Category:
MVC
Target version:
-
Start date:
2014-02-11
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

This is the forward port of the bug #55861 in TYPO3 CMS.

A typical controller call in TYPO3 CMS looks like this

    /**
     * Single view of a news record
     *
     * @param Tx_News_Domain_Model_News $news news item
     * @param integer $currentPage current page for optional pagination
     * @return void
     */
    public function detailAction(Tx_News_Domain_Model_News $news = NULL, $currentPage = 1) {
}

As long as no news property or a correct uid is given everything is ok but if the record can't be found, the exception

Exception while property mapping at property path "":Object with identity "3" not found.
is thrown.

There is currently no way for an extension, to handle this error in the own code! It is very normal, that records get deleted, set to hidden or what so ever. Therefore it must be up to the extension if a default value is set (like NULL) to return NULL by the property mapper!


Related issues

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

Actions
Related to TYPO3.Flow - Bug #8670: Non-required action argument throws Exception on unknown get-parameter uidResolvedKarsten Dambekalns2010-08-18

Actions

Also available in: Atom PDF