Published 22 February 2017
For Episerver Version 9 and later
All configurable links to imagevault, find, admin, admin content type, and logout. Even custom links!
Default menus are Admin and logout, to activate other menu items apply this appsettings: (they are sortable)
|
1 2 3 |
<appSettings> <add key="Gosso.QuickNav" value="imagevault,find,admin,contenttype,logout" /> </appSettings> |
You can add custom menu items, Name and url with pipe in between. Name can be lang resource path eg /shell/admin/logout
|
1 2 3 |
<appSettings> <add key="Gosso.QuickNav" value="Custom link|http://devblog.gosso.se,imagevault,find,admin,contenttype,logout" /> </appSettings> |
Download:
Packages are in Episerver’s NuGet feed. If not set up go to Visual Studio => NuGet Package Manager => Package Sources => Add http://nuget.episerver.com/feed/packages.svc/
|
1 2 |
Install-Package <span id="ctl00_body_PackageID">Gosso.EPiServerAddOn.QuickNavExtension</span> |
http://nuget.episerver.com/en/OtherPages/Package/?packageId=Gosso.EPiServerAddOn.QuickNavExtension
More on Github: https://github.com/LucGosso/Gosso.EPiServerAddOn.QuickNavExtension
Regards!
SEO Tems
Create an interface (e.g. IQuickNavigationMenuProvider) and give me possibility to add more menu items via code (that would make sure that I don’t need to use Xml path for resources and also will give me possibility to resolve Url at runtime, instead of config file).
And also add callback for checking whether this item is available in current context (cases when I want to add shortcut to some resource, but only for selected group of users).
No pressure, just a thug life of OSS authors 🙂
Thx!
Sure thingy Waldis! yes could do, i wanted to keep it childish simple.
The recommendation is still to use your own IQuickNavigatorItemProvider implementation if you want full control (which my code is based on)
Will see, thx for all input =)