Hide a menu link from header when member is logged it
I am wanting to customize the header navigation when a member logs in. Basically my customer has a tab that says "Why Join". They would like for that to vanish when logged in. This will allow for the navigation not to wrap or cause other issues in the navigation
I am wondering if Wild Apricot has 2 header files or any suggestions on how to handle this.
Thanks in advance.
![](https://secure.gravatar.com/avatar/e97542837f833728817bdae0b60a513f?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Larry Azus commented
We would also like this capability!
We want to be able to hide the "Join Us" page (and other pages) from members.
-
Mike Savoie commented
Would also like this feature.
Our logged in members don't need to see Sign-Up and About Us.
-
Dennis Slade commented
+1
-
Kevin commented
Fully agreed.
It is great that content is hidden from public that is member restricted.
We need the reverse, we need content to disapear once someone has joined!
So, a member joins, I no longer need the 'Join' button to be in the navigation.
This goes for other content.
It would be good to have an option to hide sales pages geared at signing up members once members actually join - they no longer require sales pages for what they have already purchased, they instead now require upsels and pages for retention purposes -
Anonymous commented
Is this still impossible to do now? Would love to be able to have public-only content that disappears once logged in.
-
Walt Bilofsky commented
I have a different application for this. I'd like our Why Join tab to be on the top menu for public visitors, but a submenu item for members.
How about a site page option for the page to be visible only to public but not to members? Then there could be two (possibly duplicate) Why Join pages, one for public only and one for members only, at different places in the menu structure?
This requires the admin (or their consultant) to do a workaround, but it should be easier to implement than multiple menu structures.