I'm attempting to structure multiple levels of site navigation by using the "Modify Navigation" setting (Site Actions > Site Settings > Modify Navigation)
But it seems the UI on that page doesn't let me create pages which are children of other pages, or create folders which are children of other folders.
Basically, I need to create not just first level/second level nesting, but also 3rd and 4th level nesting of pages
I understand the parameters to so in the default.master to control if other levels are displayed, but I can't figure out how to create such a structure in sharepoint?
Am I completely missing the point?
Out of the box, there are no "sub-pages" in navigation in MOSS. The nested navigation which Heather Solomon describes in this article is about how you create multi-level navigation of a known site/subsite hierarchy.
If you need pages and sub-pages in your navigation, you will have to create a custom editor which allows you to define the needed hierarchy, as well as you will have to create a custom "navigation provider" which knows how to navigate the hierarchy.
Related
I am building the product navigation within the Hybris CMS, but the top level links won't work without being assigned to link to a page.
I only want the top level to reveal sub-nav items when clicked or hovered over.
Is there a way to achieve this?
Go into the Hybris WCMS, go to the 'Navigation' menu in the top,left of the wcms. Than just remove all targets that are assigned to the Navigation Nodes on the top level.
BR
I am new at hybris6.x development.
I have created a new category with some products in power tools site but now I want to add that category and removing all the remaining categories in the site's category navigation bar.
How to do that? Any help will be appreciated.
Login /cmscockpit and select navigation tab from left top corner. Don't miss synchronization after modification.
The navigation bar is a cms component. It uses navigation nodes to display a navigation. Navigation nodes define a tree structure of navigation nodes. Each navigation node can have multiple link components. Link components can point to either a category, a product, a content page or a static URL. As mkysoft already said, there is a perspective in cmscockpit for defining this structure.
I'd like to have main menu in wiki part of Tiki Wiki. It should have following top-level items:
About
Atlas
Encyclopedia
Now the tricky part: I'd like to link each of above top-level menu items to corresponding structure so that hovering over Atlas opened sub-menu taken from Atlas structure.
I can make static menu like About/Atlas/Encyclopedia. I can make dynamic menu out of one structure so that top-level structure items become top-level menu items. Basically I need a menu out of structure but in such a way that it is structure's root that becomes top-level menu element. And then place three such structures horizontally.
Alternatively I could do it by nesting structures. Is it possible? And in such a way that it can be turned into nested menu?
I just stumbled over your question today and I hope my answer still can be a help for you.
Imho the right approach is to create a custom module and in the custom menu a "toplevel menu" with some simple html. The menu consists out of the three top items and for each one the appropriate structure menu as list element.
You want a horizontal menu, right?
The menu items "About", "Atlas", "Encyclopedia" representing your three wikistructures would be kind of drop down (or hover effect) horizontal css menu items level=0 (to) for example in a top-bar custom module.
You hover over one of the menu items and the associated wikistructure menu appears.
Regards,
Torsten
Well, I settled with "hybrid" solution. I have a structure like that:
Root
About
Intro
Setting
Encyclopedia
Organizations
Technology
Atlas
Inner system
Outer system
I created a "Root" page and made a Structure out of it.
Then I created first-level pages in that structure.
In next step I created those second-level pages - but as separate
pages, not part of "Root" structure.
Every such second-level entry was made a Structure and sub-pages were created in those secondary structures.
Then I added each second-level page (being a root of second-level structure) to main "Root" structure.
"Root" structure was then declared as main menu: in Manage > Modules > Assigned modules > Topbar I added "Menu" module and set structureId of "Root" structure.
So basically it's this alternative of nested structures I asked about. It does solve my problem of having tree-structure for menu that isn't overloaded by every minute page on wiki I'd like to have. On one hand it doesn't show all the entries but on the other hand it's good - the reader isn't overwhelmed and still can access deeper pages by second-level pages that have all the sub-structure listed.
I am creating a new footer sublayout in sitecore for use in multiple sites (we run a multi site environment). Currently a sublayout called StandardLayout is used, but I would like to change this across several of our sites to a new layout GlobalFooter.
The problem is that child items of the Home Page have overridden layout components, so what I would like to know is if there is an easy way to change the layout without losing all of the overridden components (as I expect that I may need to reset the layout in order for the flow down to occur)?
I am hoping to be able to just change the top level element (Home) and then have this flow down to the child elements, otherwise this task will become very long and tedious if I need to go through each item and change the presentation to use the new footer.
The icon circled in red in the image above indicates that the presentation has been overridden for that particular sitecore item.
To answer your question, directly, there is no way to apply an update of the presentation details of a template to templates that inherit from it that have had their presentation details changed without losing the changes.
The solution described in the blog post you linked to is the best solution for updating inherited presentation details in this manner. IMHO, I believe that this functionality should have been built into Sitecore long ago as a separate button on the ribbon, and you may choose to add one if you are so inclined. If you do not have the time to do so however, creating an admin page that you later delete from the site after using is a perfectly viable solution as well.
This post appears to detail a way that I can achieve my goal, basically I would create a admin page that does not publish and put the code in the blog into it to update the layout via a button trigger.
https://www.sitecore.net/Learn/Blogs/Technical-Blogs/John-West-Sitecore-Blog/Posts/2011/09/Programmatically-Update-Layout-Details-with-the-Sitecore-ASPNET-CMS.aspx
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.