Changes between Version 3 and Version 4 of 1.3/TracNavigation

Timestamp:

Oct 15, 2019, 6:28:07 AM (5 years ago)

Author:

trac

Comment:

—

1.3/TracNavigation

@@ -9 +9 @@
 
 
-** [=#Example Example] ** 
+** [=#Example Example] **
 
 In the following example we rename the link to WikiStart //Home//, and make the //View Tickets// entry link to a specific report.
@@ -26 +26 @@
 [[comment(see also #Trac3808)]]
 
-** Example ** 
+** Example **
 
 {{{#!ini
@@ -63 +63 @@
 }}}
 
-Attributes of the navigation item that are not overridden by the configuration will be preserved. 
+Attributes of the navigation item that are not overridden by the configuration will be preserved.
 
 === URL Formats
@@ -98 +98 @@
 
 === Permissions #nav-permissions
-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. 
+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.
 
 For 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.