Anyway to show a Nav item for both logged-out AND specific logged-in users? – II

Hi Steve,

I expected that as Administrator was higher than Customer they should at least see the Customer menu items, possibly all menu items.

This is generally correct. The plugin relies on current_user_can() to decide if a user has the correct capabilities to view a menu item. So most of the time, an admin has the capability. Though it can happen that you haven’t assigned a specific cap to the admin user.

But first you should check if there’s a conflict coming from somewhere. Can you reproduce the issue with a default theme and only NMR plus whatever is defining the customer role.

Then you should check if a customer’s capabilities are also assigned to the admin… Generally on plugin activation.

Hope that helps.

Thanks Helga.
I didn’t understand “you haven’t assigned a specific cap to the admin user”.

However I think it is to do with when I enable the following snippet:

function my_wp_nav_menu_args( $args = '' ) {
if( is_user_logged_in() ) { 
    $args['menu'] = 'Customer';
} else { 
    $args['menu'] = 'Public';
} 
    return $args;
}
add_filter( 'wp_nav_menu_args', 'my_wp_nav_menu_args' );

When enabled this seems to work for not logged in (public), and Logged in as Customer (Customer menu) but when logged in as Administrator I lose all the menus.

However if I tick Customer AND Administrator on the Customer menus I see the Customer Menus in the Administrator screen (but not the Public Menus)!

My head hurts….:-)

Any ideas?

Thank you!
Cheers
…Steve

One of the limitations of NMR is that is checks if the menu item is visible “by role” when “by capability” is more accurate. Roles are a lot friendlier though, and mostly they work, so I use that. If for example, a Customer role has only a “can_do_awesome_stuff” capability, but the administrator does not also have the “can_do_awesome_stuff” capability, then the admin would not be able to see the menu item designated for the Customer. Compare that to a core “Subscriber” role which has capabilities such as “read_posts” which the Admin role also has. Because of that, admins can see menu items set for subscribers.

You may want to read about roles and capabilities:

Roles and Capabilities

Anyway, that snippet seems like you are trying to swap out the entire menu based on whether a user is logged in/out. That’s beyond what NMR does and I wouldn’t recommend trying to mix the two concepts. I think you can simplify things by using your snippet to swap menus between users, or use NMR to swap individual menu items between users.

OK, I understand – thank you very much. I do like NMR and would like to make that work as it is easier on the other site admins who aren’t as tech-savvy as me (and I’m not tech savvy anyway!), so I’ll try and work out the best way of achieving my outcome:-)

Keep up the good work, Helga!

Cheers
…Steve

Sorry Helga, I’m still struggling with this.

I hadn’t realised that Customer wasn’t a standard role (don’t know where it came from!), so I’ve now changed the names and roles used to use Subscriber for the “Subscriber” menu.

So now I have three types of views:
1. Not logged in – sees the ‘public’ menus
2. Logged in as Subscriber – sees the ‘Subscriber’ menus
3. Logged in as Administrator – Want to see ‘public’ menus with Dashboard.

Public menu items are set to Everyone can view, Subscriber menu items are set to Subscriber (and above) can view.

[In case it wasn’t clear before, the Public and the Subscriber menus are separate Menu structures – does that make a difference?]

(I’ll add a button or menu item (I hope) to click between Public, Dashboard and Subscriber views for Administrators – that’s another mini-project!)

NOW however, all three scenarios above see the Public menu – none see the Subscriber menu.

I’ve checked and triple-checked that the Subscriber menu items all have Logged in mode set to Subscriber role and the Public menu items have “Everyone” set. I’ve run it on Twenty-Nineteen with all plugins except NMR deactivated and it’s the same.

Any ideas? Thanks for your patience:-)

Cheers
…Steve