Top navigation & footer navigation share some items

Dennis Hulsmans asked on January 29, 2016 16:25

I'm struggling with the menu structures of a site. The customer wants to "share" some links in separate menus. For example a contact link in the top menu, which is visible in the footer menu too. These should link to the same page (same url).

How can I achieve this? How can you have a visible separation in the pages module between those menus. I tried using folders, but the folder name will become visible within the URL. For example: www.mywebsite.com/contact will become www.mywebsite.com/footer/contact I tried using linked pages too, but I'm unable to solve the issue with the urls

Thx for the help!

KR, D.

Correct Answer

Brenden Kehren answered on January 29, 2016 17:11

I find the easier and more robust solution is to create a "Navigation" category in the Categories app and then nest another below it for "Top", "Main", "Footer", etc. Then on the page, assign the categories you want. Then in your webparts, set the categories you want to display. No need to try to capture all the possible scenarios in the MenuItemGroup field because it just isn't possible.

3 votesVote for this answer Unmark Correct answer

Recent Answers

Rui Wang answered on January 29, 2016 16:30 (last edited on January 29, 2016 16:30)

Hi Dennis

You can use the Form tab field Menu group for that. Set something like Header only or Footer only as to others can be showing in both places.

Then in the WHERE condition of the list control you use for menu, you can add condition like this for header menu MenuItemGroup <> 'footer' OR MenuItemGroup IS NULL

Which excludes footer only items.

1 votesVote for this answer Mark as a Correct answer

Zach Perry answered on January 29, 2016 16:40

I would use Rui's suggestion of menu groups,but if you want to use linked pages, and want to solve the URL issue, you can use page alias's to change the URL.

0 votesVote for this answer Mark as a Correct answer

Chetan Sharma answered on January 30, 2016 05:39

Hi, I could think of two possible solutions to this.

1.First solution is on the same lines as Brenden has already suggested. I would create a field in page Type Menu Group and have many values to it like "Header", "Footer" and use that field in the where clause of my repeater/webpart to get the right data.

2.Second solution is that if you have all these pages as a separate page types then I can use content filter property to load right page type in my webpart and render them accordingly using the right transformation.

The kind of websites we make we often come across solution 2 as we make many page types and then leverage it.

Thanks, Chetan

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on February 1, 2016 06:46

The problem with adding a field to a page type is it's a one to one relationship. If you use a category, you can have a one to many relationship. It offers a more robust solution for all scenarios with little effort.

0 votesVote for this answer Mark as a Correct answer

Tobania Kentico answered on February 1, 2016 14:59 (last edited on February 1, 2016 14:59)

0 votesVote for this answer Mark as a Correct answer

Dennis Hulsmans answered on February 1, 2016 15:01 (last edited on February 1, 2016 15:42)

Hi all,

First of all thanks for all the responses!! I tried the menugroupitem thingy, but I'm not sure this is the best way, so I'm going to try Brendens approach.

The only downside I see is that it's not that "visible" and "easy" for a customer with limited knowledge to change things. It's always some clicks before they can see to which menu a page belongs.

I'll keep you posted, and thanks again for all the replies.

Other ideas are welcome too, I'm just trying to figure out which is the easiest to maintain.

Also my apologies for the answer above, I noticed I was logged on with the wrong account :)

Thx, D.

0 votesVote for this answer Mark as a Correct answer

Dennis Hulsmans answered on February 4, 2016 11:00 (last edited on February 4, 2016 11:54)

Do you use the category approach together with a basic repeater instead of a category list (menu) web part? Or is it easier to create a custom web part based on a css list menu web part and extend it with category filtering? I'm just thinking from a customer perspective, so the customer can easily change some of these things

0 votesVote for this answer Mark as a Correct answer