Project

General

Profile

Actions

Bug #38249

closed

TSConfig: t3lib_befunc::getTCEFORM_TSconfig() not considering non-array values when building conf

Added by Jerome Schneider almost 12 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Miscellaneous
Target version:
-
Start date:
2012-06-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:

Description

in t3lib_befunc::getTCEFORM_TSconfig(), non array values are not added to the returned conf array.

Exemple: this TSConfig, set in a page, is not considered nor returned by the method:
TCEFORM.tt_content.hello = World

Whereas this one is:
TCEFORM.tt_content.hello.dear = World

This is due to the fact that line 3223 if (is_array($val)) { processes only array values to merge them in the resulting conf array, whiteout counterpart for non-array values (no else).

To fix this, add these instructions at line 3230:

} else {
    $res[$key] = $val;
}

This impacts a lot of things (for me, the inability to set TCEFORM.tt_content._STORAGE_PID from Page TSConfig), and I suspect that many bugs in the BT are related to this (noticeably #30864)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #30864: userTSconfig: TCAdefaults.tt_content.imagecols = 1 does not workClosed2011-10-12

Actions
Actions #1

Updated by Gerrit Code Review about 11 years ago

  • Status changed from New to Under Review

Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at https://review.typo3.org/19895

Actions #2

Updated by Wouter Wolters over 9 years ago

  • Status changed from Under Review to Needs Feedback
  • Is Regression set to No

Hi,

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

Actions #3

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to Closed

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

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