Project

General

Profile

Actions

Bug #98148

closed

Extbase persistence erronously tries to persist unmapped private property

Added by Christian Ebert almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
Start date:
2022-08-16
Due date:
% Done:

100%

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

Description

TYPO3 11.5.14
Currently when persisting a domain model with an internal private property which should not be persisted to the database a "Cannot access private property ..." error occurs. So far as I can see this was introduced with the latest changes applied with commit e92d3212e5990d525b71ac967445add7e994b8c1 . In 11.5.13 this error not occurs. There is also no TCA Configuration for the property.

The error is triggered in:
/typo3/sysext/extbase/Classes/DomainObject/AbstractDomainObject.php line 131
at TYPO3\CMS\Extbase\DomainObject\AbstractDomainObject->_getProperty('solicitor')
in /var/www/html/www/public/typo3/sysext/extbase/Classes/Persistence/Generic/Backend.php line 598
at TYPO3\CMS\Extbase\Persistence\Generic\Backend->insertObject
in /var/www/html/www/public/typo3/sysext/extbase/Classes/Persistence/Generic/Backend.php line 281

The domain model is as follows:

class Quote extends AbstractEntity
{

    private ?\MyNamespace\Solicitor $solicitor;

}

Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Bug #95819: Extbase does not support uninitialized domain object propertiesClosedAlexander Schnitzler2021-10-30

Actions
Related to TYPO3 Core - Bug #98190: Extbase fails to resolve chained validationsAccepted

Actions
Actions

Also available in: Atom PDF