The Custom User Menu theme component, created by manuel, adds a dropdown menu to the header for quick access to personal settings and pages, replacing the default profile tab in the notifications menu. It is available via GitLab and can be installed using the provided guide. The component separates notifications from the user menu, improving navigation. user2 praises its design, while StryGuardian notes a conflict with the F NAV Mobile Navigation Tabs component, which also modifies the header. manuel acknowledges the issue, explaining that both components target similar UI elements, causing UX and style conflicts. StryGuardian suggests conditional activation based on screen size and component presence, which manuel agrees to implement by adding a dedicated mobile style. digitaldominica confirms the conflict, while jrgong reports no issues on their setup and asks if PRs are accepted. Hyteller inquires about mobile support, and manuel clarifies that while the menu works on mobile, a dedicated mobile modal is planned for future updates.
It seems there is a small conflict between this and F NAV Mobile Navigation Tabs, which moves the Notification bell to the bottom of the screen. It still functions fine, but where the bell should be in the header, it’s just a blank space. Tapping that blank space opens the same menu as tapping my profile picture.
Thanks for pointing this out! I don’t see how I’d make this compatible though.. Using both components at the same time will likely lead to other ux and style conflicts, as they essentially introduce the same menu, but with slightly different template implementations.
I can only speak for myself and my particular use case, but I would love to be able to utilize this component for desktop/laptop use and have it “step aside” on mobile and let the tabs component do the work.
The only thing I could think of would be to have this component look for the tabs component and the size of the display. The tabs component is only active on mobile, so perhaps it could work as designed on large screens and if tabs is active, turn off on smaller screens. I have no idea what kind of work that would require or if it’s even possible.
I’ll add a dedicated mobile style a bit down the line. Then you can use this component for the user menu, also on mobile. And the footer navigation from the other component. This should actually align just fine.
Do you still have the issue? I just tested my own F NAV fork on 3.5.1 with this TC and it works like a charm…
@manuel do you accept PRs? It would be a nice addition to display the username in bold when full names are disabled in site settings and also link the user’s avatar to his profile “summary”
No. To be clear, the menu as such works on mobile. But I didn’t have a client that needed a dedicated mobile modal or compatibility with mobile navigation tabs of the above mentioned component.
Roadmap
