Changes between Version 3 and Version 4 of TracNavigation


Ignore:
Timestamp:
Feb 1, 2021, 2:06:05 PM (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracNavigation

    v3 v4  
    99
    1010
    11 ** [=#Example Example] ** 
     11** [=#Example Example] **
    1212
    1313In the following example we rename the link to WikiStart //Home//, and make the //View Tickets// entry link to a specific report.
    … …  
    2626[[comment(see also #Trac3808)]]
    2727
    28 ** Example ** 
     28** Example **
    2929
    3030{{{#!ini
    … …  
    6363}}}
    6464
    65 Attributes of the navigation item that are not overridden by the configuration will be preserved. 
     65Attributes of the navigation item that are not overridden by the configuration will be preserved.
    6666
    6767=== URL Formats
    … …  
    9898
    9999=== Permissions #nav-permissions
    100 The `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. 
     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.
    101101
    102102For 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.