Oh, duh! .special=directory works great when you put the second TMENU in. I
think I might actually use directory menus exclusively from now on. I can't
believe I've been struggling with this for a week.

Code snippet follows:

THIS_SITE.menuLeft = HMENU
THIS_SITE.menuLeft.special = directory
THIS_SITE.menuLeft.special.value = 395 # start of page tree
THIS_SITE.menuLeft.1 = TMENU
THIS_SITE.menuLeft.1 {
wrap = <div>Left Menu Title<br>|</div>
NO {
stdWrap.cObject = COA
stdWrap.cObject {
10 = TEXT
10.field = title
wrap = |<br>
}
}
}
THIS_SITE.menuLeft.2 = TMENU
THIS_SITE.menuLeft.2 {
NO {
stdWrap.cObject = COA
stdWrap.cObject {
10 = TEXT
10.field = title
wrap = |<br>
}
}
}

-------------------------
James Corell
EPCS, 111 W. Mitchell St. Suite E, Gaylord, MI 49735
DSL for Businesses - Websites That Work!
jcorell (AT) e-p-c-s (DOT) com www.e-p-c-s.com
989-732-1366 (fax 989-732-0893)



-----Original Message-----
From: typo3-english-bounces (AT) lists (DOT) netfielders.de
[mailto:typo3-english-bounces (AT) lists (DOT) netfielders.de]On Behalf Of
Christopher Torgalson
Sent: Friday, May 11, 2007 4:30 PM
To: TYPO3 English
Subject: Re: [TYPO3] HMENU and entryLevel with multiple trees (top menu
/left menu)


On 5/11/07, James Corell <jcorell (AT) e-p-c-s (DOT) com> wrote:
> As I noted in my original post, I've already been all over .special. I am
> using .excludeUidList in my makshift attempt at producing split-tree
menus.
> So far, the documentation has NOT been my friend.
>
> Again: I would like to be able to specify a start-point for a menu and
have
> it cascade from there (by PID, not level). Anyone else?


If you've 'been all over .special,' what happened when you used
".special = directory"?


--
Christopher Torgalson
http://www.typo3apprentice.com/
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

There probably is a better solution, but I just don't know what that would
be. Ideally you could use regular HMENUs and TMENUs to build two separate
trees for menus, but what happens when you enter a different tree from the
one you are currently at? Your menus change to reflect your new position in
the hierarchy.

The easiest way I've found to handle this is to create 2 trees at the
rootline, one for the top menu and another for the left menu. Then, using
..special=directory, create menus. This allows content editors to create and
delete pages, and I don't have to edit the template every time they do.

-------------------------
James Corell
EPCS, 111 W. Mitchell St. Suite E, Gaylord, MI 49735
DSL for Businesses - Websites That Work!
jcorell (AT) e-p-c-s (DOT) com www.e-p-c-s.com
989-732-1366 (fax 989-732-0893)



-----Original Message-----
From: typo3-english-bounces (AT) lists (DOT) netfielders.de
[mailto:typo3-english-bounces (AT) lists (DOT) netfielders.de]On Behalf Of Tomas
Mrozek
Sent: Sunday, May 13, 2007 3:00 PM
To: typo3-english (AT) lists (DOT) netfielders.de
Subject: Re: [TYPO3] HMENU and entryLevel with multiple trees (top menu
/left menu)


> Oh, duh! .special=directory works great...

Yeah, that's what I tried to push you at.

There's only one problem:
The whole idea of populating menus by TypoScript is wrong since it goes
against the point of CMS - customers manage the site (Customer's
Managment of the System ) and since only admins can chnage TS template...

I personally think that there's a smoother solution.

Tomas Mrozek
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english