Changes between Version 14 and Version 15 of MenusPlugin


Ignore:
Timestamp:
Dec 22, 2008, 1:16:44 PM (6 years ago)
Author:
izzy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MenusPlugin

    v14 v15  
    3030||label||What should be written on the "button"||Team Tools||
    3131||href||Where the item should link to||/report/1||
    32 ||enabled||Should it be used? Hell, why we define it? But this is useful to temporarily disable an item.||1||
     32||enabled||Must be set to `1` for self defined items to be shown. Can be set to `0` to (temporarily) disable an item.||1||
    3333||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||
    3434||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||
    3535||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||
    36 ||path_info||To be matched with the request path info.||??||
     36||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||
    3737
    3838,,Missing here: `inherit`,,
     
    5757
    5858[mainnav]
    59 # Create a new top-level element for "Team Tools"
     59# Create a new top-level element for "Team Tools" - make sure to set it to "enabled" or it doesn't show up!
    6060teamtools = enabled
    6161teamtools.parent = top