Project

General

Profile

Actions
Copy link

Feature #33584

closed

checkIF for each TypoScript content objects (cObjects)

Added by Michael Birchler over 12 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-02-01
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently the checkIf method is only for certain cObjects (HMENU, CASE, IMAGE, stdWrap)
valid, all other cObjects are ignored.

This behaviour makes no sense to me and the TypoScript code gets unnecessarily bloated.

Example:
  1. doesn't work
    10 = CONTENT
    10 {
    #ignored
    if.isTrue.data = GP:tx_ttnews|tt_news

table = tt_news
    select {
}
        renderObj = COA
        renderObj {
                10 = TEXT
                10.field = title
        }
}

works but code gets bloated
  1. works but code gets bloated
    10 = COA
    10 {
    10 = CONTENT
    10 {
    if.isTrue.data = GP:tx_ttnews|tt_news

table = tt_news
                select {
}
                renderObj = COA
                renderObj {
                        10 = TEXT
                        10.field = title
                }
        }
}

Related issues 1 (0 open — 1 closed)

Has duplicate TYPO3 Core - Bug #63342: stdWrap.if rendered also when negativeClosed2014-11-26

Actions
Actions
Copy link
 #1

Updated by Michael Birchler over 12 years ago

A clean example:

10 = CONTENT
10 {
        #ignored
        if.isTrue.data = GP:tx_ttnews|tt_news

        table = tt_news
        select {

        }
        renderObj = COA
        renderObj {
                10 = TEXT
                10.field = title
        }
}

10 = COA
10 {
        #works
        if.isTrue.data = GP:tx_ttnews|tt_news

        10 = CONTENT
        10 {

                table = tt_news
                select {

                }
                renderObj = COA
                renderObj {
                        10 = TEXT
                        10.field = title
                }
        }
}

Actions
Copy link
 #2

Updated by Alexander Opitz over 9 years ago

  • Status changed from New to Needs Feedback

Hi,

does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?

Actions
Copy link
 #3

Updated by Gerrit Code Review about 9 years ago

  • Status changed from Needs Feedback to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36817

Actions
Copy link
 #4

Updated by Gerrit Code Review about 9 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36817

Actions
Copy link
 #5

Updated by Gerrit Code Review about 9 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/36817

Actions
Copy link
 #6

Updated by Mathias Schreiber about 8 years ago

  • Status changed from Under Review to Closed
Actions
Copy link

Also available in: Atom PDF