Default menus versus member menus display.php question

[david-wpck]

My question is about having 2 separate registered menu types.
I did read the thread about removing a menu on a specific page, but I need to go a little further then that.

One set (default Jump Start menus) for non members and visitors.
Second set would be a mirror of the first set with “members” add to the name.

So I want to have:
Primary Navigation
Primary Member Navigation
Footer Navigation
Footer Member Navigation

I can register the new menus just fine so that’s not a problem.

My question is about the framework/frontend/functions/display.php where the menu is shown.

If I just created a conditional “else, if” to show the normal “Primary” menu versus the “Primary Member” menu, would this be the appropriate file to do that?
Or, do you see a better way to accomplish this?

What I basically want is to show completely different menus to members versus visitors.

Topic

[Jason Bobich]

Hello,

Yeah, I’d agree, and say that’s what you want to do.

Here’s how I’d suggest setting that up — First you’d copy the “themeblvd_header_menu_default” function to your Child theme’s functions.php. Then change the name of the function to something unique and and add in your if/else statements for displaying your different instances of wp_nav_menu. And then you’d unhook the framework’s function and hook in your new one to the “themeblvd_header_menu” action hook.

function my_header_menu(){
	// ...
}
remove_action( 'themeblvd_header_menu', 'themeblvd_header_menu_default' );
add_action( 'themeblvd_header_menu', 'my_header_menu' );

… And then the same thing for the footer menu.

http://dev.themeblvd.com/tutorial/actions/

http://dev.themeblvd.com/tutorial/primary-framework-action-hooks/

[david-wpck]

Excellent. Thanks for the swift reply.
P.S. – Like what you’ve done with the Jump Start coding, well thought out and structured, just the way it should be.

[Jason Bobich]

Thanks, David. I appreciate it.

[Author]

Replies