App menu missing after upgrade to 31

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.4
  • Operating system and version (e.g., Ubuntu 24.04):
    • Debian 12
  • Web server and version (e.g, Apache 2.4.25):
    • Apache 2.4.62
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • n/a
  • PHP version (e.g, 8.3):
    • 8.2.28
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • upgrade to 31.0.4
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • bare metal
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

After the upgrade from 30.0.8 to 31.0.4 the app menu in the web frontend disappeared.
The only way to display it is to click on the Nextcloud logo (top left) and then three dots appear, after clicking the bar expands with the list of apps.

Steps to replicate it (hint: details matter!):

  1. open Nextcloud in web browser (I’m using Firefox 128.9.0esr)

Log entries

No error as far as I can see in both Nextcloud or Apache log.

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Enabled:
  - activity: 4.0.0
  - app_api: 5.0.2
  - bookmarks: 15.1.0
  - bruteforcesettings: 4.0.0
  - calendar: 5.2.2
  - circles: 31.0.0
  - cloud_federation_api: 1.14.0
  - comments: 1.21.0
  - contacts: 7.0.6
  - contactsinteraction: 1.12.0
  - dashboard: 7.11.0
  - dav: 1.33.0
  - federatedfilesharing: 1.21.0
  - federation: 1.21.0
  - files: 2.3.1
  - files_downloadlimit: 4.0.0
  - files_external: 1.23.0
  - files_pdfviewer: 4.0.0
  - files_reminders: 1.4.0
  - files_sharing: 1.23.1
  - files_trashbin: 1.21.0
  - files_versions: 1.24.0
  - firstrunwizard: 4.0.0
  - logreader: 4.0.0
  - lookup_server_connector: 1.19.0
  - news: 25.3.1
  - nextcloud_announcements: 3.0.0
  - notes: 4.12.0
  - notifications: 4.0.0
  - oauth2: 1.19.1
  - passman: 2.4.12
  - password_policy: 3.0.0
  - photos: 4.0.0-dev.1
  - privacy: 3.0.0
  - profile: 1.0.0
  - provisioning_api: 1.21.0
  - recommendations: 4.0.0
  - related_resources: 2.0.0
  - serverinfo: 3.0.0
  - settings: 1.14.0
  - sharebymail: 1.21.0
  - spreed: 21.0.3
  - support: 3.0.0
  - survey_client: 3.0.0
  - systemtags: 1.21.1
  - tasks: 0.16.1
  - text: 5.0.0
  - theming: 2.6.1
  - twofactor_backupcodes: 1.20.0
  - twofactor_totp: 13.0.0-dev.0
  - updatenotification: 1.21.0
  - user_status: 1.11.0
  - viewer: 4.0.0
  - weather_status: 1.11.0
  - webhook_listeners: 1.2.0
  - workflowengine: 2.13.0
Disabled:
  - admin_audit: 1.21.0
  - encryption: 2.19.0
  - suspicious_login: 9.0.1
  - twofactor_nextcloud_notification: 5.0.0
  - user_ldap: 1.22.0

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

You didn’t fill out the support template so can’t say with certainly, but sounds like you have a third-party app such as Custom Menu (aka: side_menu) installed.

Thanks for looking at it, I’ve updated the list of apps in the OP. No, I don’t have “Custom Menu” installed.

So turns out this is a browser issue.

The problem does not exist in Google Chrome 135 or Firefox 137.
It seems to exist in Firefox 128 (I believe this is the default in my outdated Debian 11 - I really need to upgrade my desktop sooner rather than later.

However the problem only appeared after the upgrade of NC to 31.

Are you sure it’s an old-Firefox problem and not a caching problem:

Does it work in a private window of Firefox 128?

1 Like

Actually - you are right, in a new private window of FF 128 I cannot reproduce the issue (all works as expected).

Previously I only tried to log out and log in in my other “normal” FF 128 window and I still could see the problem, so I assumed.

1 Like

@mritzmann can you pls recommend a solution here, do I need to delete all cached data for my NC site from my browser? Thanks

Try reloading the page without cache by pressing CTRL + F5.

2 Likes

Thank you, that did the trick.
I’m on Linux so in my case it was “Ctrl + Shift + R” (had to google that).

2 Likes

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.