nextcloud / nextcloud/deck

Attachments not linked to card - files are still there

Open
#5,228 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Describe the bug

I found out today that several cards that had attachments are now missing them. One card even shows them in the Android App, but I see only a placeholder thumbnail (all are images).

In the history of each card, I see that I added the attachment, but when I click on the filename, I get a JSON with content {"status":403,"message":"Permission denied"}.

The files that were originally attached are however still in Nextcloud, i.e., in the Deck folder.

I have no idea when this happened - it must have been an update in the past 6 Months though.

Other cards still have attachments - I haven't checked all my cards though, thus I'm not even sure what the pattern is.
My only suspicion is, that these are all files I have uploaded via the Deck Android App - but I'm not 100% sure about that.

I checked the oc_deck_attachment table, and I cannot see the files there.

Is there anything else I can check? I might be able to recover backups from some months ago and could check the database there, but that would take some time.
Would it be possible to go through the history of all cards (where is this stored though?), check if files were attached, then check if these files are still in nextcloud and re-attach them?

To Reproduce
Steps to reproduce the behavior:

  1. Create a card, add attachments
  2. ??? - sorry, cannot reproduce :(

Expected behavior
Attachments should not be removed from card

Client details:
Independent of Client

Server details

Operating system:
Debian

Web server:
nginx

Database:
psql

PHP version:
8.2

Nextcloud version: (see Nextcloud admin page)
27.1.2

Where did you install Nextcloud from:
nextcloud

Signing status:

Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or

Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...

Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...

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 inspecting the oc_deck_attachment table and the card history to determine how attachments uploaded through the Android app became unlinked while remaining in the Deck folder. Compare affected and unaffected cards, then verify that attachment associations persist and that existing files can still be opened after the fix.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.