Deck List (Column) Order Not as set in Desktop and Does Not Match Deck Mobile App List
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
To Reproduce
Steps to reproduce the behavior:
- Go to Deck module
- Click on Deck List and view columns
- View Deck List on Mobile Deck app
- The order of columns in the Deck, the list, is not in the same order as how I arranged it originally and it does not match the Deck mobile app Deck list view. The mobile Deck app orders the columns correctly.
Expected behavior
That the desktop Deck list columns order would be the same as the mobile Deck app list column order.
Screenshots
See screenshots of the mobile app deck list and the desktop browser view of the Deck list column order.
Client details:
- OS: Android
- Browser Firefox, Deck Android app
- Version Firefox 121.0 & Deck app 1.23.4
- Device: Samsung Fold 4
Operating system:
Web server: Nextcloud AIO, Nextcloud Hub 6 (27.1.4)
Database:
PHP version:
Nextcloud version: (see Nextcloud admin page)
Where did you install Nextcloud from:
Signing status:
"system": {
"one-click-instance": true,
"one-click-instance.user-limit": 100,
"memcache.local": "\OC\Memcache\APCu",
"apps_paths": [
{
"path": "/var/www/html/apps",
"url": "/apps",
"writable": false
},
{
"path": "/var/www/html/custom_apps",
"url": "/custom_apps",
"writable": true
}
],
"appsallowlist": [],
"check_data_directory_permissions": false,
"memcache.distributed": "\OC\Memcache\Redis",
"memcache.locking": "\OC\Memcache\Redis",
"redis": {
"host": "REMOVED SENSITIVE VALUE",
"password": "REMOVED SENSITIVE VALUE",
"port": 6379
},
"overwritehost": "cloud.com",
"overwriteprotocol": "https",
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"localhost",
"cloud.com"
],
"datadirectory": "REMOVED SENSITIVE VALUE",
"dbtype": "pgsql",
"version": "27.1.4.1",
"overwrite.cli.url": "https://cloud.com/",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbport": "",
"dbtableprefix": "oc_",
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"instanceid": "REMOVED SENSITIVE VALUE",
"maintenance": false,
"loglevel": "2",
"log_type": "file",
"logfile": "/var/www/html/data/nextcloud.log",
"log_rotate_size": "10485760",
"log.condition": {
"apps": [
"admin_audit"
]
},
"preview_max_x": "2048",
"preview_max_y": "2048",
"jpeg_quality": "60",
"enabledPreviewProviders": {
"1": "OC\Preview\Image",
"2": "OC\Preview\MarkDown",
"3": "OC\Preview\MP3",
"4": "OC\Preview\TXT",
"5": "OC\Preview\OpenDocument",
"6": "OC\Preview\Movie",
"7": "OC\Preview\Krita",
"0": "OC\Preview\Imaginary"
},
"enable_previews": true,
"upgrade.disable-web": true,
"mail_smtpmode": "smtp",
"trashbin_retention_obligation": "auto, 30",
"versions_retention_obligation": "auto, 30",
"activity_expire_days": "30",
"simpleSignUpLink.shown": false,
"share_folder": "/Shared",
"one-click-instance.link": "https://nextcloud.com/all-in-one/",
"upgrade.cli-upgrade-link": "https://github.com/nextcloud/all-in-one/discussions/2726",
"updatedirectory": "/nc-updater",
"davstorage.request_timeout": 3600,
"htaccess.RewriteBase": "/",
"dbpersistent": false,
"files_external_allow_create_new_local": false,
"trusted_proxies": "REMOVED SENSITIVE VALUE",
"allow_local_remote_servers": true,
"preview_imaginary_url": "http://nextcloud-aio-imaginary:9000",
"mail_from_address": "REMOVED SENSITIVE VALUE",
"mail_sendmailmode": "smtp",
"mail_domain": "REMOVED SENSITIVE VALUE",
"mail_smtphost": "REMOVED SENSITIVE VALUE",
"mail_smtpauth": 1,
"mail_smtpport": "465",
"mail_smtpname": "REMOVED SENSITIVE VALUE",
"mail_smtppassword": "REMOVED SENSITIVE VALUE"
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Deck module's desktop Deck List and compare its column-order behavior with the mobile Deck app list shown in the issue. Reproduce the ordering after arranging columns, then verify that the desktop list preserves the chosen order and matches mobile. Done means both views display columns in the same order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100