[TYPO3-core] RFC #11224: Special menu directory only renders 1st level if special.value is a mount point
Xavier Perseguers
typo3 at perseguers.ch
Sun Jul 12 13:30:29 CEST 2009
Hi Franz,
>> Problem:
>> Create a directory menu with special.value being a mount point
>> (Substitute Mount Point (this page) with Mounted page is not set). E.g.,
>>
>> lib.menu = HMENU
>> lib.menu.special = directory
>> lib.menu.special.value = 6
>>
>> lib.menu.1 = TMENU
>> lib.menu.1 {
>> expAll = 0
>> # standard configuration for NO, CUR, ...
>> }
>> lib.menu.2 < lib.menu.1
>> lib.menu.3 < lib.menu.2
>>
>> 1st level is shown but once an entry from 1st level become active, 2nd
>> level (and of course 3rd level will never be shown).
>
> isn't there a related issue to "special=directory" in bugtracker? Can't
> have a look ATM as bugtracker is still down for maintenance :(. I only
Don't know, yes bugtracker is much more down than only "shortly".
> remember that I had a similar issue with menus once where also one vital
> information did not get passed to the child records and thus sublevels
> failed. Would be nice if this could also be fixed in that step.
I only found this problem when using sysfolders and mount points. If you
remember what the problem was, I may find out whether it is related.
--
Xavier Perseguers
http://xavier.perseguers.ch/en
One contribution a day keeps the fork away
More information about the TYPO3-team-core
mailing list