Project

General

Profile

Actions

Bug #55941

closed

Content Object instances are reused

Added by Oliver Hader about 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2014-02-12
Due date:
% Done:

100%

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

Description

The ContentObjectRenderer creates instances for each content object to be rendered, e.g. TEXT, COA, CONTENT, etc.
However, these instances are re-used and therefore we introduced work-arounds since serialization of FLUIDTEMPLATE failed back then.
If dealing with nested record sets via RECORDS or CONTENT, reusing objects might be tricky since the parent pointer to the ContentObjectRenderer might be wrong and strange things happen.

This patch removes the pseudo singleton approach since the objects are not state-less and might lead to unexpected results in rare cases.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #55297: Cleanup ContentObject\ContentObjectRendererClosed2014-01-07

Actions
Actions

Also available in: Atom PDF