Project

General

Profile

Actions

Bug #64916

closed

Avoid serialization of some members of ContentObjectRenderer

Added by Markus Klein almost 10 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Backend API
Target version:
Start date:
2015-02-06
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
hard
Is Regression:
No
Sprint Focus:
Stabilization Sprint

Description

UserInternalContentObject is trying to serialize ContentObjectRenderer.
This leads to severe issues also uses lots of memory.

If you set up a page like this

page = PAGE
page.10 < styles.content.get
page.20 < plugin.tx_felogin_pi1

Install sysext:felogin and add static templates for CSC and felogin!

Add a "text w/image" CE to the page and add at least one image.

you'll get an Exception in FE: Serialization of closure not possible.

(In order to see the Exception you need to set the application context to Development and select the Development-preset in Install Tool.)

The reason is that if the Core is not installed via composer, a closure is registered in the SignalSlotDispatcher.
For some reason, when serializing ContentObjectRenderer, also SignalSlotDispatcher is serialized, which leads to this exception.

The solution is to remove the "hard-wires" between ContentObjectRenderer and TSFE and File(Reference).


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #64376: Class aliases not respected in certain situationsClosed2015-01-20

Actions
Related to TYPO3 Core - Bug #77645: Closures in SignalSlot\Dispatcher can cause troublesClosed2016-08-26

Actions
Actions

Also available in: Atom PDF