Does Attachment > Share from Files Duplicate Files/Folders? Or merely links?

[reidellawfirm]

I noticed after starting to attach my existing Nextcloud files using the Attachments > Share from Files modal that there is now duplicate folders and files in a root 'Deck' folder in my NC instance. It appears there are duplicated as when I search for a file, it appears both in the original folder that I linked to a Deck card and again in the 'Deck' folder in the root directory.

But I also noticed that revisions or additions to only the folder/file in the root 'Deck; folder is also replicated in the originally linked file/folder. So there is some linking being done but I am unsure whether there the root 'Deck' folder is merely a linked reference or if it is a duplication of the original files/folder that then also updates the original.

I am looking to keep my file/folder structure more lean and do not want duplication of working folders/files but I cannot find any specific details in the documentation about this. Please point me in the right direction to find more details.

[luka-nextcloud]

Thanks for your submission. I cannot reproduce this issue. Please share system report and reproduce steps.
Something like this:

[reidellawfirm]

So Deck does not create a separate folder in the root NC directory for attachments by default?

Or was yoru response an automatic copy paste because you didn't see your checklist items and refused to read it?

[reidellawfirm]

Version
Nextcloud Hub 9 (30.0.5)

Operating System: Linux 5.15.0-131-generic x86_64

CPU: Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz (2 threads)

Memory: 15.61 GB

PHP
Version: 8.3.16

Memory limit: 1 GB

Max execution time: 3600

Upload max size: 16 GB

OPcache Revalidate Frequency: 60

Extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, hash, iconv, json, mbstring, SPL, session, PDO, pdo_sqlite, bz2, posix, random, readline, Reflection, standard, SimpleXML, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, cgi-fcgi, apcu, bcmath, Phar, exif, ftp, gd, gmp, igbinary, imagick, imap, intl, ldap, memcached, pcntl, pdo_pgsql, pgsql, redis, smbclient, sodium, sysvsem, zip, libsmbclient, Zend OPcache

Database
Type: pgsql

Version: PostgreSQL 16.6 on x86_64-pc-linux-musl, compiled by gcc (Alpine 14.2.0) 14.2.0, 64-bit

Size: 370.6 MB

[luka-nextcloud]

@reidellawfirm
I have checked on v30 but cannot reproduce this issue.

• There are no duplicate files when using Attachments > Share from Files feature
• The Deck folder is only created to store files from Attachments > Upload new files feature. There are no duplicate files for that functionality
• It would be great if you could provide the steps to reproduce the issue

[reidellawfirm]

Understood, thank you. Then this is tied to my creation of Deck cards and attachments through webhook/API. Let me review this further, I am not sure if it is an artifact of my webhook/API request or if it is a result of NC attachment process.

[reidellawfirm]

@luka-nextcloud

Per my team looking further into this:

We checked the Deck folder in our NextCloud account and found that when attaching a folder to a Deck Card from the web UI, no corresponding Case_File (the folders we use to hold documents and which we link to Deck cards) linked folders were created. To test this, we manually created a folder under Case_File, then created a Deck Card (screenshot) and assigned the folder to it using the "Share from Files" method.

After enabling sharing, the Case_FIle folder also appeared in the root NC Deck folder. To verify whether it was a linked reference or a duplicate, we renamed the folder in Case_File (screenshot) and checked if the change reflected in the Deck folder (screenshot). The name remained unchanged. However, when we modified the share link settings in Case_File, the changes were reflected in the Deck folder. Additionally, when we deleted the folder from Case_File, it was automatically removed from the Deck folder.

We also noticed that the folder ID remained the same in both Case_File and Deck, confirming that the folders inside the Deck folder are linked references rather than duplicates.

For further clarification, please review the attached screencast video, and let me know if you have any questions.

So it seems that when an attached folder is shared in NC (we have group shares which I believe triggered the Deck folder links) then a Deck folder in the NC root director is created that holds a link to the attached documents that are shared. It is not a duplicate but a link.

I don't mind the behavior as long as it was not duplicating folders/files and reducing my storage space available which it is not currently.