Top Menu not populating options

Product Support

AI-generated summary

The discussion revolves around the top menu not displaying all configured options in Discourse, affecting both custom and default themes. Heliosurge reports the issue, showing screenshots of the menu and admin settings. JammyDodger explains that the unread and new tabs are intentionally hidden when empty, but provides CSS code to force their display. Heliosurge appreciates the solution and plans to test it. Moin adds context, noting the feature was introduced in 2018 and that users with trust level 0 may still see these tabs. He also references a GitHub code snippet and suggests the Experimental new new view groups setting might explain why the ‘new’ tab remains visible.

1

I am running latest Test-Passed (3.5…)

In ghost Theme and air Theme the top menu on main page is not giving all options configured in admin . Note also affects default themes.

The image shows a screenshot of a website interface, highlighting the "(year) Pockets Nexu" tab and the "Announcements" category with an unconfirmed VIP access for "Planet Pimax" in the "Latest" section. (Captioned by AI)
The image shows a screenshot of a website interface, highlighting the "(year) Pockets Nexu" tab and the "Announcements" category with an unconfirmed VIP access for "Planet Pimax" in the "Latest" section. (Captioned by AI)864×1920 165 KB

Admin too menu config

This image shows the "site settings" page for a Discourse website, detailing options for the top menu categories. (Captioned by AI)
This image shows the "site settings" page for a Discourse website, detailing options for the top menu categories. (Captioned by AI)864×1920 160 KB

How would I fix this?

2

I’m not sure it’s broken as such. The unread and new tabs are deliberately hidden when there’s nothing to see. :magic_wand:

Though I think it is possible to force them to reveal themselves even when empty if that’s what you had in mind?

Maybe something like this?

// for desktop

.navigation-container .nav-pills .nav-item_new {
    
    display: initial !important;
}

.navigation-container .nav-pills .nav-item_unread {
    
    display: initial !important;
}

// for mobile

.dropdown-menu .nav-item_new {
    
    display: initial !important;
}

.dropdown-menu .nav-item_unread {
    
    display: initial !important;
}
3

Thank you Jam. Will need to test this out. The one pic showing it is stable at that time. So I am guessing they added the hide if not populated later in.

Will have to run one of my test users

Thanks for the code to restore past behavior.

4

I think that was added in 2018

I think there is some magic so users with trust level 0 see new and unread even when they are empty, so they can learn they exist.

Maybe Experimental new new view groups is why you only see ‘new’? That also prevents new from being hidden.