nextcloud / nextcloud/server

[Bug]: App Order can not be changed reliable

Open
#55,266 9 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 32-feedback bug
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Whenever I try to change the app order in the navigation bar settings they get moved back to the original position after reload.

Steps to reproduce
  1. I changed my app order many months/years ago. The current oder looks like this:
Image
  1. When I want to change it, e.g. swap the two first apps in the menu, the request returns 200:
  2. But if I reload nothing changed.
  3. I can use "reset default app order", this works. After reload I have again the default order.
Image
  1. Now the really strange thing start to happen
  2. I now want to change the app order based in the default order
  3. I swap again the first and the second app, the request returns again 200
  4. Sometimes it works sometimes not but latest if I continue to do additional changes, e.g. move the calendar from the back to the front within multiple steps or move more than one app and than reload strange things start to happens. Sometimes changes are simply not applied, sometimes other elements moved in parallel... for me it is completely unpredictable. If you just play a bit around you should be able to reproduce it hopefully.
Expected behavior

consistent and verifiable behavior if I move apps around.

Tested on c.nc.com (32.0.0 RC3)

Nextcloud Server version

32

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Reproduce the app-order changes in the navigation settings, then trace the request and reload path; done means reordered apps persist consistently after reload without unrelated items moving.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
backend, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.