TYPO3 Core

Does the domain model object (or any of it's relations) contain for example a Logger or similar? Basically the error says that you have a closure somewhere in the object structure to be serialized, which you should probably unset (or use __sleep/wakeup) before serialisation.

Just want to mention that this issue also appears now in latest 9.5.17.

Probably some of the models is using a File or FileReference - in that's my assumption is true, the problem is the same as in #91196 (files having an instance of EventDispatcher, which has Closures).

@Oliver - there are no file or FileReference relations in these models.

The models only have References to other models (ObjectReference) and to the sys_categories

I just updated to 10.4.3 but the issue is the same.

I doublechecked everything once more. It is definitly an issue with the relations in the model.
As soon as I'd remove all relations from it (even those to itself) the serialization is working.

As said I only have Relations (via ObjectStorage incl. @Lazy) to sys_category and the Product Model itself and a Document model.
Product as well as Document doesn't have any closures inside.

This is really an issue cause it prevents us not only from upgrading to 10 but also within the 9 LTS version.

Can be closed. It seems to be fixed with 9.5.19
I'll also check this in v10 during this weekend.

I can confirm this for 10.4.20. Just changed some properties of my model to "Lazy", now "serialize()" throws this error.

Can confirm this still occurs, TYPO3 version 10.4.27.

Simple reproduction:
-Use a domain model with an @lazy property, for example ext:news domain model News:

```
/** * Fal media items * * @var \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\GeorgRinger\News\Domain\Model\FileReference> * @TYPO3\CMS\Extbase\Annotation\ORM\Lazy
*/
protected $falMedia;

```

When this property is used in extbase form the VH `Web/typo3/sysext/fluid/Classes/ViewHelpers/FormViewHelper.php` will try to serialize:

```
$result .= '<input type="hidden" name="' . htmlspecialchars($this->prefixFieldName('__referrer[arguments]')) . '" value="' . htmlspecialchars($this->hashService->appendHmac(base64_encode(serialize($request->getArguments())))) . '" />' . LF;

```

Then the exception of the closure will occur.

I can also confirm it with TYPO3 10.4.28.

Reproduction:
Use the Form ViewHelper with a domain model having a relation to a system category (which has a @lazy definition on its parent property).

/**
 * @var \TYPO3\CMS\Extbase\Domain\Model\Category|null
 * @Extbase\ORM\Lazy
*/
protected $parent;

(1/1) Exception

Serialization of 'Closure' is not allowed

in /var/www/html/private/typo3/sysext/fluid/Classes/ViewHelpers/FormViewHelper.php line 291

$result .= '<input type="hidden" name="' . htmlspecialchars($this->prefixFieldName('__referrer[arguments]')) . '" value="' . htmlspecialchars($this->hashService->appendHmac(base64_encode(serialize($request->getArguments())))) . '" />' . LF;

Damn! I hit this very problem in TYPO3 v10 :(

I hacked by passing an integer (uid) instead of the object to the method I'm possibly forwarding to. That solves that bug.

Background (as I ran into this problem as well) is IMHO:

I have a relation which is bi-directional (imagine "$material->getCategories()" and "$category->getMaterials()") which both have the lazy attribute, which I had used in a Extbase form. Removing the attribute resulted into a PHP memory error. Removing one of the relations (which I did not need directly), made it work.