Project

General

Profile

Actions

Bug #23181

closed

Separate first template optically

Added by Bernhard Kraft over 14 years ago. Updated almost 11 years ago.

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

0%

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

Description

When having multiple TS-Templates on one page, only the first one will get used. The other ones can still get included using the "Include Basis Template". But by default only the first TS-Template on every page will get used. This is also stated in the last comment of this (early) bug report:

http://bugs.typo3.org/view.php?id=2041#c4595

I think it would make sense, to separate the first TS-Template on every page from the other ones, so a Admin can easily notice that only the constants/settings in the first template will get used.

I explicitly added not screen mockup so some of you UI designers can let their ideas flow.

(issue imported from #M15117)

Actions #1

Updated by Bernhard Kraft over 14 years ago

This behaviour (only use first template) is cause by t3lib/class.t3lib_tstemplate.php in line 502:

$res = $GLOBALS['TYPO3_DB']->exec_SELECTquery('*', 'sys_template', 'pid='.intval($this->absoluteRootLine[$a]['uid']).$addC.' '.$this->whereClause,'','sorting',1);
if ($row = $GLOBALS['TYPO3_DB']->sql_fetch_assoc($res)) {

.... The "limit" parameter of SELECTquery is set to "1" and there is no "while ($row =" but rather an "if ($row =" for fetching the TS-Template(s).

Actions #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • TYPO3 Version set to 4.3
  • 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 #3

Updated by Alexander Opitz almost 11 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