Project

General

Profile

Actions

Bug #49684

closed

Menu/Sitemap type Section Index

Added by Johannes C. Laxander over 11 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-07-05
Due date:
% Done:

0%

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

Description

I've a TYPO3 4.7.12-Installation with gridelements 1.3.12 (the Website based on a backend layout). A content element "Menu/Sitemap" with type "Section Index" is not displayed, if the content column is colPos=11, because TYPO3 reders all content elements with colPos=0 by default.

Joe Hasnau give me this tip: tt_content.menu.20.3.1.sectionIndex = 1 (http://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/Sectionindex/Index.html).
But it doesn't work. The "old setting" tt_content.menu.20.3.select.where = colPos=11 doesn't work also.

Actions #1

Updated by Stefan Galinski over 11 years ago

  • Status changed from New to Needs Feedback

From the documentation:

.sectionIndex.useColPos = [integer /stdWrap]

(Since TYPO3 6.0) This property allows you to set the colPos which should be used in the where clause of the query. Possible values are integers, default is "0".

Any positive integer and 0 will lead to a where clause containing "colPos=x" with x being the aforementioned integer. A negative value drops the filter "colPos=x" completely.

Like you see the feature was introduced in TYPO3 6.0. The old setting should work if you switch to the 4.6 version of the css_styled_content template.

Actions #2

Updated by Johannes C. Laxander over 11 years ago

Many Thanks! Yet, it works fine!

Actions #3

Updated by Stefan Galinski over 11 years ago

  • Status changed from Needs Feedback to Resolved
Actions #4

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF