I try to figure out what's the best strategy to manage a menu in Asp.Net and highlight the "active" menu-item.
That's have to be done in the MasterPage but it's the Page that know what menu-item to highlight.
I have found that implementing a custom SQL Site Map Provider combined with impementing a fully custom menu component, one just need to render the menu html depending on the application/design etc. For intance I have just recently implemented the jQuery Superfish Menu using our Menu component.
jQuery is great for searching and selecting particular classes/elements and applying styles/classes as required.
Some Helpful URLS:
http://users.tpg.com.au/j_birch/plugins/superfish/
http://msdn.microsoft.com/en-us/magazine/cc163657.aspx
http://dotnetslackers.com/VB_NET/re-17169_Rendering_a_databound_UL_menu.aspx
HTH
Related
I have a liferay theme for version 7.3. I am facing one problem in the theme's menu.
Now menu has some static items. How can I change (add / remove) items dynamically by admin account?
The menu is added in /src/templates/portal_normal.ftl as
<#include "${full_templates_path}/menu-bar.ftl" />
this file has static html data.
Now how can I make it dynamic so that admin can change the menu items?
Make the menu as a web content, and drag it to the theme? Not makes sense because menu is the part of the theme.
Or any other way of picking the menu items, looping the items in .ftl and display it?
The times of scripting navigation and menus in the theme are over, and I'd rather recommend to embed a portlet in your theme that does the job. That might be a stock NavigationMenu portlet (see how Liferay's default "classic theme" does this with NavigationMenu or the SearchBar), or a custom one, which generates exactly what you'd like.
Reason: It's a lot simpler to redeploy a new portlet and generate/test appropriate HTML markup generation in a portlet than it is to implement proper error handling in a theme's freemarker script.
The solution can be if you want to add your data in navigation menu in themes, go into the navigation menus inside site builder in menu and create a new menu by clicking + button on top right and name the menu. Then go into the pages inside site builder inside menu. There will be a + sign on public pages. Click that and add a page that you want to list. If you want to create a submenu then on the page that is created, create a subpage by clicking there + sign. The page will be child and will be shown as a sub menu in theme.
I'm new using ghost, it's possible create this using ghost?
If you are asking if there is an easy way to create a dropdown menu from the ghost backend i am afraid there is none.
You can find a navigation.hbs in the standard theme (Casper) partials folder that you could style as you wish.
Or you can search for a theme that has dropdowns implemented.
In the source code for a master page, there is a section that has the following ASP.NET item: . This contains the "Welcome (User Name)" and Site Actions menus.
How do I create an additional menu that is similar to the look and feel of the Welcome menu? I've tried to create Front End HTML that behaves similar to the out of the box SharePoint menus, but it isn't quite right. I would prefer to utilize an ASP.NET or SharePoint control that acts similar to the SharePoint menu if that is possible.
For example, is <SharePoint:AspMenu> the appropriate control to use?
Thanks,
Robert
i am sure you will get better answer than this but just wanted to point what i have done to do this
i have added javascript library (JQuery) (for some other reason ) and when time come to do this thing i just added a JQuery code that creates another item in the navigation list with appropriate style and css class with the needed link and caption.
You could try another instance of the PersonalActions control with a custom GroupId. But when the control is rendered, it might also say "Welcome, [User]" just like the original.
I added a new page in the main menu, e.g. Products. Now I want to add a subpage e.g. Sub Products below a Products page. I tried all possible options in the dashboard but it didn't work for me. Any ideas how to handle this?
Thanks.
here is a quick solution for this
Go to your dash board -->Gallery -->Modules
search for Hierarchical menu and install it
after installing then go to Configuration -->Features and enable it.
Go go to Navigation .give position like 2 for "Products" and 2.1 for "Sub products".
you will see Sub products appear under Products page.
As of Orchard CMS 1.5 this is supported by the core navigation module. Now you can simply drag and drop menu items under one another in the Admin -> Navigation view. You can then control level rendering under the widget settings for the menu by setting the "Start level" and "Levels to display" properties.
See release notes for further details.
The navigation documentation doesn't seem to be up to date though :(
Take a look at: http://orchard.codeplex.com/Thread/View.aspx?ThreadId=242327
The module to support this (along with many other modules) is available in Orchard's module gallery.
How can I customise the Site Actions menu to remove or rename 'standard' menu items? Where are the site actions menu items defined?
The site actions menu is defined in the Siteaction.xml in Template\layouts\editingMenu under the 12 hive. The following link shows how to manually remove items.
Customize Site Actions Menu
I have added options to the menu using features, but have never tried to hide OTB option in code. I would be interested in your results.
Good luck!
I was able to hide the menu item I wanted to hide by using ConfigMenu="Delete" in the relevant XML node of SiteActions.xml. e.g.
<ConsoleNode ConfigMenu="Delete" ChangedNodeID="wsaCreateSite" />
The valid values for ConfigMenu are documented at http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.publishing.webcontrols.configmenuoptions.aspx
I have used a control that runs javascript to hide the entire site actions menu for users of a certain privelege level.
That approach may be an option if you need to remove items for particular users.
It is not the worlds classiest approach however.