Remove Navigation Tab?

[RobParker]

Our problem is that we have too many tabs in our navigation bar and I was wondering what the easiest way to remove the tab would be?

Even better would be to have one tab for both the Sortsbook and the Pick'em addons but I suspect we're in the minority wanting that.

 

[Bob]

The easiest is to disable the Code Event Listener for the specific tab.

Steps:

1. Put your site into debug mode.

2. Click on the Development Tab

3. Click on Code Event Listeners

This will list ALL code event listeners for Addons that you've added. What you want to do is disable the navigation_tabs listener for Pickem. To disable, simply uncheck the box for that specific listener. If you ever want to enable it again, you simply check the box. You can do this for ANY addon that has a navigations_tab listener.

 

[RobParker]

I never realised it was that easy, that's a huge help

It sounds like I should be able to disable the tab for both sportsbook and Pickem and then use a page node as a "landing page" for both of them.

Cheers

 

[Bob]

yuppers... you should be able to do that You'll need create sub navigation links tho so that people can get to specific areas like the leaderboard and the My Picks page..

 

[Sheldon]

I think when you disable them that way, you will also lose the breadcrumb on them. At least it happened for me. Then the members complained about the breadcrumb not being there. Meh. Just can't win. Hah.

 

[Sheldon]

Here was one I created combining Sportsbook and Stock Trader. I am sure you can replace whatever is needed for PickEm as well.

<ul class="secondaryContent blockLinksList">
        <div class="primaryContent menuHeader muted"><a href="/sportsbook/">Sportsbook</a></div>
    <li><a href="{xen:link 'sportsbook-events'}">{xen:phrase xi_sportsbook_menu_item_events}</a></li>
    <li><a href="{xen:link 'sportsbook-events/archive'}">{xen:phrase xi_sportsbook_menu_item_events_archive}</a></li>   
    <li><a href="{xen:link 'sportsbook-wagers'}">{xen:phrase xi_sportsbook_menu_item_my_wagers}</a></li>
    <li><a href="{xen:link 'sportsbook-stats'}">{xen:phrase xi_sportsbook_menu_item_statistics}</a></li>
    <xen:if is="{$visitor.permissions.xisportsbook.createEvent}">
        <li><a href="{xen:link 'sportsbook-bookiecp'}">{xen:phrase xi_sportsbook_menu_item_bookiecp}</a></li>
    </xen:if>
    <div class="primaryContent menuHeader muted"><a href="/stocktrader/">Stock Trader</a></div>
    <li><a href="{xen:link 'stocktrader/top-portfolios'}">Top Portfolios</a></li>
    <li><a href="{xen:link 'stocktrader/popular-stocks'}">Popular Stocks</a></li>
    <li><a href="{xen:link 'stocktrader'}">My Portfolio</a></li>
</ul>

 

[Bob]

You can get away with that as long as all the URLs are static (which all of those are). If there are any variables involved used to create dynamic URLs(which pickem will have), that are passed via listeners or controllers, then you will have a problem.

 

[Sheldon]

You can get away with that as long as all the URLs are static (which all of those are). If there are any variables involved used to create dynamic URLs(which pickem will have), that are passed via listeners or controllers, then you will have a problem.

Completely forgot about the fact there would be dynamic URLs.