Changes between Initial Version and Version 1 of TracNavigation

Jul 30, 2021, 7:40:25 AM (16 months ago)



  • TracNavigation

    v1 v1  
     1= Trac Navigation
     3The main and meta navigation entries can be customized in several ways. The `[mainnav]` and `[metanav]` configuration sections can be used to customize the navigation item text and link, change the ordering of the navigation items, disable them and add new ones.
     5The primary attributes that can be customized are `href`, `label`, `order` and `permission`.
     7=== `[mainnav]` #mainnav-bar
     8`[mainnav]` corresponds to the '''main navigation bar''', the one containing entries such as ''Wiki'', ''Timeline'', ''Roadmap'', ''Browse Source'' and so on. This navigation bar is meant to access the default page of the main modules enabled in Trac that are accessible for the current user.
     11** [=#Example Example] **
     13In the following example we rename the link to WikiStart //Home//, and make the //View Tickets// entry link to a specific report.
     16wiki.label = Home
     17tickets.href = /report/24
     20Note the entries on the main navigation are displayed in uppercase regardless of the casing of the `label`, unless this aspect of the styling is overridden through [TracInterfaceCustomization#SiteAppearance interface customization].
     22=== `[metanav]` #metanav-bar
     23`[metanav]` corresponds to the '''meta navigation bar''', by default positioned above the main navigation bar and below the ''Search'' box. It contains the ''Login'', ''Logout'', ''!Help/Guide'' etc. entries. This navigation bar is meant to access some global information about the Trac project and the current user.
     25There is one special entry in the  `[metanav]` section: `logout.redirect` is the page the user sees after hitting the logout button.  The ''!Help/Guide'' link is also hidden in the following example.
     26[[comment(see also #Trac3808)]]
     28** Example **
     32help = disabled
     33logout.redirect = wiki/Logout
     36=== Extra Navigation Entries #nav-extra-entries
     38New navigation entries can be arbitrarily defined and added
     39to the navigation. A new entry can be defined by providing a name with value `enabled`. At a minimum, the `href` attribute should be specified to define a useful navigation entry. If the `label` attribute is not defined the entry's name will be used for the label.
     41The following example creates two new navigation items, one named //My Reports// and the other named //builds//. //My Reports// is only visible to users with `REPORT_VIEW` permission.
     44myreports = enabled
     45myreports.href = /report/9
     46myreports.label = My Reports
     47myreports.permission = REPORT_VIEW
     50builds = enabled
     51builds.href =
     54The entry names are always read as lowercase, as is the case for all keys in the trac.ini file due to the way the configuration parser is configured. If the example above used `BUILDS` rather than `builds` for the name, the entry would still be displayed as `builds`. Use the `label` attribute for case-sensitive customization of the navigation entry text.
     56=== Relocating Entries #nav-relocating-entries
     58Navigation entries provided by Trac and plugins can be moved from the meta navigation bar to the main navigation bar, and vise-versa. The entry should be defined in the desired category as if it was a new entry. For example, to move the //Admin// entry to the metanav and rename it to //Administration//:
     61admin = enabled
     62admin.label = Administration
     65Attributes of the navigation item that are not overridden by the configuration will be preserved.
     67=== URL Formats
     68Possible URL formats for `.href` or `.redirect`:
     69|| '''config''' || '''redirect to''' ||
     70|| `wiki/Logout` || `/projects/env/wiki/Logout` ||
     71|| `http://hostname/` || `http://hostname/` ||
     72|| `/projects` || `/projects` ||
     75=== Ordering #nav-order
     76The `order` attribute specifies the order in which the navigation items are displayed. This can be particularly useful for plugins that add navigation items.
     78Non-negative floating point values may be used for the `order` attribute. The navigation items will be arranged from left to right in increasing order. Navigation items without an `order` attribute are sorted alphabetically by name.
     80The default values are:
     83browser.order = 4
     84newticket.order = 6
     85roadmap.order = 3
     86search.order = 7
     87tickets.order = 5
     88timeline.order = 2
     89wiki.order = 1
     92about.order = 5
     93help.order = 4
     94login.order = 1
     95logout.order = 2
     96prefs.order = 3
     99=== Permissions #nav-permissions
     100The `permission` attribute controls the visibility of the navigation item on the navigation bar. This is mainly useful for new entries in the navigation bar. Note that it does not provide access control to the URL that the navigation item directs to, and cannot override permission checks done by Trac and plugins.
     102For example, the //Roadmap// navigation item will only display for users with `ROADMAP_VIEW`. Adding the attribute `roadmap.permission = MILESTONE_VIEW` will require both `ROADMAP_VIEW` and `MILESTONE_VIEW` for the entry to be visible, but as noted will not provide access control for the `/roadmap` path. TracFineGrainedPermissions should be used for access control to modules provided by Trac and plugins.
     104=== Context Navigation #ctxtnav-bar
     106Note that it is still not possible to customize the '''contextual navigation bar''', i.e. the one usually placed below the main navigation bar.
     109See also: TracInterfaceCustomization