nextcloud / nextcloud/deck

Once you create an attachment through "share from files", share link cannot be created by others

Open
#3,533 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: attachments feature: sharing
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

If a file is attached to a deck using "Share from files", then others cannot create a share link for that file. NC gives the following pop up message: "Error creating the share: Cannot increase permissions of ..."

Steps to reproduce the behavior:

  1. User Jack, Mary and Nicole are members of Group Team.
  2. User Jack shares the folder X with Group Team.
  3. Board A is also shared with Group Team.
  4. Mary creates a card within Board A and attach a folder Y within folder X.
  5. Nicole cannot create a share link for folder Y. (Error creating the share: Cannot increase permissions of ...)

Expected behavior
Nicole should be able to create a share link for folder Y. By the way, Resharing is enabled on the Nextcloud instance.

As soon as Attachment is removed from the deck card, all members of Group Team are able to create a share for folder Y.

Client details:

  • OS: Windows, Ubuntu
  • Browser: Firefox
  • Device: Desktop

Server Details
Operating system: Almalinux 8.5
Web server: Apache 2.4.37
Database: MariaDB 10.3.28
PHP version: 7.4.27
Nextcloud version: 23.0.0
Where did you install Nextcloud from: Manual

List of activated apps:

  - accessibility: 1.9.0
  - activity: 2.15.0
  - announcementcenter: 6.1.1
  - appointments: 1.11.10
  - apporder: 0.14.0
  - approval: 1.0.9
  - bookmarks: 10.0.3
  - bruteforcesettings: 2.3.0
  - calendar: 3.0.4
  - circles: 23.0.0
  - cloud_federation_api: 1.6.0
  - collectives: 0.17.22
  - comments: 1.13.0
  - contacts: 4.0.7
  - contactsinteraction: 1.4.0
  - dav: 1.21.0
  - deck: 1.6.0
  - drawio: 1.0.2
  - emlviewer: 1.0.0
  - external: 3.10.2
  - extract: 1.3.3
  - federatedfilesharing: 1.13.0
  - federation: 1.13.0
  - files: 1.18.0
  - files_antivirus: 3.2.2
  - files_downloadactivity: 1.12.0
  - files_external: 1.15.0
  - files_fulltextsearch: 23.0.0
  - files_pdfviewer: 2.4.0
  - files_rightclick: 1.2.0
  - files_sharing: 1.15.0
  - files_trashbin: 1.13.0
  - files_versions: 1.16.0
  - files_videoplayer: 1.12.0
  - fileslibreofficeedit: 1.0.4
  - firstrunwizard: 2.12.0
  - fulltextsearch: 23.0.0
  - fulltextsearch_elasticsearch: 23.0.0
  - impersonate: 1.10.0
  - integration_suitecrm: 1.0.3
  - logreader: 2.8.0
  - lookup_server_connector: 1.11.0
  - maps: 0.1.10
  - nextcloud_announcements: 1.12.0
  - notes: 4.3.0
  - notifications: 2.11.1
  - oauth2: 1.11.0
  - onlyoffice: 7.2.1
  - password_policy: 1.13.0
  - photos: 1.5.0
  - privacy: 1.7.0
  - provisioning_api: 1.13.0
  - ransomware_protection: 1.12.0
  - recommendations: 1.2.0
  - serverinfo: 1.13.0
  - settings: 1.5.0
  - sharebymail: 1.13.0
  - spreed: 13.0.1
  - support: 1.6.0
  - survey_client: 1.11.0
  - systemtags: 1.13.0
  - tasks: 0.14.2
  - text: 3.4.0
  - theming: 1.14.0
  - twofactor_backupcodes: 1.12.0
  - twofactor_totp: 6.2.0
  - updatenotification: 1.13.0
  - user_status: 1.3.1
  - viewer: 1.7.0
  - weather_status: 1.3.0
  - workflowengine: 2.5.0

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

Start by reproducing the reported Deck attachment and share-link flow with the stated group permissions, then trace how the attached folder's permissions are evaluated when Nicole creates a share. Done means that removing the attachment is no longer necessary and Nicole can create a share link for folder Y.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.