Dear list:

I've been all over the documentation, and through more than a few examples
and how-to's, but I can't figure out how to do this. It seems like it would
be possible, but how?

I have a page tree like this:

Site Root
Home <- contains TS, TSConfig, and is a link to "Page 1"
Top Menu <- shortcut type to "Page 1"
Page 1
Page 2
Page 3
Page A
Page B
Page i
Page ii
Page iii
Page C
Page 4
Left Menu <- shortcut type to "Page 5"
Page 5
Page 6
Page 7
Sitemap <- hidden in menu

I'd like to have the top menu look like this:
Page 1
Page 2
Page 3
Page A
Page B
Page C
Page 4

and the left menu to look like this:
Page 5
Page 6
Page 7

I would think I could set the startPid of the HMENU (somehow) and let TYPO3
do the rest, but entryLevel mangles my top and left menus when I switch to
pages in other trees.

Any ideas?

-------------------------
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)

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

The documentation is your friend:
http://typo3.org/documentation/docum...1.0/view/8/11/


You might be interested in the properties "special" and "excludeUidList".

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

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

> 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

> There probably is a better solution...

I think so. I was actually partly suggesting...

> The easiest way I've found to handle this is to create 2 trees at the
> rootline...

The problem of this is that it affects generated URLs if you are using
RealURL, for you have one useless level.

What I was playing with lately is using the property "Layout" in the
page properties.

Assumptions:
-----------
1. I have no other use for it (actually, I don't know what it was meant for)

2. The content of the pulldown menu can be modified:
http://castor.t3o.punkt.de/files/podkast_arnd.m4v (40 MB)
http://typo3.org/documentation/docum...1/3/#id3541144

3. The value set is accessible: column "layout" in the table "pages'

4. You can populate the menu yourself by your own PHP function.

So...
-----
1. ...you can change the pulldown menu:

TCEFORM.pages {
layout {
disabled = 0
altLabels {
0 = Top menu
1 = Left menu
}
removeItems = 2,3
}
}

2. ...and populate the menus by your own function:

subparts.TOPMENU = HMENU
subparts.TOPMENU.special = userfunction
subparts.TOPMENU.special {
userFunc = user_myClass->myMenu
layout = 0
}

subparts.LEFTMENU = HMENU
subparts.LEFTMENU.special = userfunction
subparts.LEFTMENU.special {
userFunc = user_myClass->myMenu
layout = 1
}

3. ...while the function "myMenu" would look something like:

class user_myClass {
function mymenu($content,$conf) {
$menuPosition = $conf['layout'];
$menuContent = array();

/* your own logic to load the pages from 'pages' table
* by your SQL query that contains
* statement WHERE layout = menuPosition
* and that populates the array $menuContent */

return $menuContent;
}
}

This way editors can choose which menu the page goes in by selecting
appropriate "layout".

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