TYPO3 Core

This problem seems to depend on the entryLevel of the special=directory type. I've had the same problem as long as the special.value was a page in the 2nd level of the rootline. If I moved the pages one level up, the special.directory worked again.
As a workaround I used special=list and set the first level to doNotShowLink=1 ~:-(

It's not a bug, it's a feature.

greets,
MB

see TSref:
http://typo3.org/documentation/document-library/references/doc_core_tsref/current/view/8/11/#id2866058

Sorry for re-opening, but if this really is a feature and not a bug, then at least the documentation is misleading (which you've linked):
"Submenus by menuPbjects 2+ will be created as usual"

Nevertheless, I don't see why it should be a feature to limit the special=directory menu type to just one level, and only under certain conditions (see Axel's note).

As usual means without any special option.
special=directory is the feature that you get only the level where pid = value and not more. Please ask on the mailinglist, if you have questions with this feature.

I still do not agree because
a) it works for nested levels if for special=directory the special.value is a page on the first level of the tree
b) it worked at least in v. 3.7.1 (just checked) and the TSRef did not change at this point since then
c) special=list DOES work with nested levels from starting points deeper in the rootline, but according to your interpretation of TSRef shouldn't do,
so it IS worth a bug report.

Axel, I cannot confirm c) here: it also does not display entries "below" those listed in special.value for menuObj>1..

well, I'm having c) up and running here, but maybe it works because the page on treeLevel 2 ($uid_menustart) has the "is root of website" attribute set?

lib.menuLeft {
special = list
special.value = {$uid_menustart}
1 = TMENU
1.NO.doNotShowLink = 1
2 = TMENU
2....

I don't understand for what reason the sublevels are limited in the core - besides it is nonsense in my eyes. If I don't need the sublevels I simply don't add them to my HMENU. This is really not the expected behaviour and I call it a bug. And it is a bug, because if I add "expAll = 1" to the first menu level the submenus are shown as expected.

Yes - the documentation says it fetches ONLY the pages with the given PID - but that means for the first level of the menu. It doesn't say that any sublevels are not fetched.

As workaround you can use conditions:
[PIDupinRootline = "pid of directory"]
lib.myMenu.special >
lib.myMenu.entryLevel = "corresponding level"
[/global]

100% ACK with Franz-Xaver Koch.

i currently solved this problem with for me an a similar hack as described above

10 = HMENU
10.special = directory
10.special.value = 20
10.1 = TMENU
......
[PIDinRootline = 20]
10.special >
10.entryLevel = 1
[END]

it works but i have to say that i also expected the same behavior like alex. a directory is for me a tree structure. i would describe the current behavior as "special.subpages" not als "special.directory".

Hy there, I fully acknowledge with those, calling this a bug! And I don't understand why one would call this a feature (if one can achieve the same result with just leaving HMENU Level 2 and up empty, but no chance to the thing the other way around) and discussing it, instead of fixing this asap... Caus it's still present in Typo3 4.1.1 and it makes special = directory really useless!!!

Tank you Martin and Franz for the reported workarounds (and for reporting this bug too!). It was a gerat help to me!

I would call this a bug, too. The param special=directory should indeed show the page structure below the entrypoint.

I recently set up a page with two different menu structures, both contained underneath two different pages (or directories). With the entrylevel set to 1, both menus worked fine, but did not show up on the home page. With the entrylevel set to 0, they showed up at home, but did not unfold their structure. So, this I would say is very well a bug.

How should a customer otherwise be able to dynamically create pages in one of those structures, without editing TypoScript menus. And content management is all about adding pages dynamically, right?

@martin ficzel : your hack works very well, thanks.for that.

So, if this IS a feature, and not a bug, I'd like to suggest adding a param to control the structure depth of that directory to be displayed, something like 'depth'.
Default value is '1', that is the current situation, integers greater then 1 for deeper level rendering, 0 for unlimeted.

100% ACK with Nils Clark-Bernhard.

Most people do not know this feature and wonder why they do not get submenues with "special = directory".

so could this be changed? there is really a need to show level 2 menues with special = directory!

ok just seen http://bugs.typo3.org/view.php?id=633

This issue was fixed in TYPO3 4.1.2.
Closed during Bug Day 07/2008