Project

General

Profile

Actions

Bug #24018

closed

Content from different page not rendered correctly with CONTENT

Added by Christoph Christ about 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-11-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

If I want to show content from other pages, I can select those like this (this is set up with templavoila and typoscript_object_path):

lib.contentLeft = CONTENT
lib.contentLeft {
table = tt_content
select {
pidInList = 24
leftjoin = pages ON
andWhere = INSTR>0 and tt_content.deleted=0
languageField = sys_language_uid
}
}

lib.contentRight = CONTENT
lib.contentRight {
table = tt_content
select {
pidInList = 62
leftjoin = pages ON
andWhere = INSTR>0 and tt_content.deleted=0
languageField = sys_language_uid
}
}

The contentLeft is working and showing correctly the contents from the particular page, but contentRight refuses to render the Flexible content Elements from contentRight (only non FCE elements are rendered correctly).

If I disable contentLeft, contentRight is shown correctly, but when I reactivate contentLeft, contentRight FCE's are ignored again.

this is reproducable on 4.4.4, 4.4.3 and 4.4.2

In earlier Typo3 Versions this was working flawlessly
(issue imported from #M16348)

Actions #1

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #2

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this ticket.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF