= MenusPlugin = == Description == - add items to navigation menus - hierachical organization(using Superfish - http://users.tpg.com.au/j_birch/plugins/superfish/ ) PS: - CSS work might be needed to fit your trac theme. == Demo == See it in action: http://code.optaros.com/trac/oforge/ == Bugs/Feature Requests == Existing bugs and feature requests for MenusPlugin are [query:component=MenusPlugin&order=priority here]. If you have any issues, create a [/newticket?component=MenusPlugin&owner=cbalan new ticket]. == Download, Source == Download the [download:menusplugin zipped source], check out MenusPlugin from [/svn/menusplugin using Subversion], or [source:menusplugin browse the source] with Trac. == Configuration == As usual, configuration takes place in the `trac.ini` file. Most interesting things first - they are to be found in the `[mainnav]` section: Here you set up your menu items. Syntax is: `. = ` - where `` is either the already existing handler (e.g. "wiki" for the wiki item, "tickets" for the tickets, "newticket" for the "New Ticket" item, a.s.o.) - or a term which ''must not exist'' for a brand new item to be introduced (as e.g. the "Team Tools" in the [#Example Examples] section). A special case is e.g. `top` to make a new item appearing on top level. === Defining your menus in the `[mainnav]` section === So here come the available properties and their possible values: ||'''Property'''||'''Description'''||'''Example value'''|| ||parent||Make the item a sub-item to the one mentioned as value||top|| ||label||What should be written on the "button"||Team Tools|| ||href||Where the item should link to||/report/1|| ||enabled||Must be set to `1` for self defined items to be shown. Can be set to `0` to (temporarily) disable an item.||1|| ||hide_if_no_children||Don't display this (sub) menu if it has no children (e.g. the current user lacks the privileges for all sub-items)||1|| ||perm||For items like reports, `hide_if_disabled` does not work, since this is no component. Though, it should not be displayed if it is not available. So you can handle this by defining the required permission.||REPORT_VIEW|| ||order||Move an item to the left/right. By default, all items have an order of 999 (who will ever reach 999 items must have done something wrong, really!). Use values from 1..999 to define positions. Use a negative value for an item you want to make sure it always comes first - and a value larger than 999 if it sould always come last.||5|| ||path_info||String to be matched with the request path info to decide whether a menu item should be displayed. Useful for context dependent items (e.g. in the ctxnav)||/wiki|| Menu options: - '''inherit''': Useful when a menu should receive items from another menu {{{ # dummy example - add mainnav items to context menu. [ctxtnav] inherit= mainnav }}} === Defining the behaviour in the `[menu-custom]` section === Here you can (re-)define (i.e. customize) the behavior of MenusPlugin. Usually, you won't need that - since the defaults are fine. But in case you need a toy to play with - here we go: Syntax is quite easy, it's just `