Cannot export cards' attachments
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
I am in the process of migrating a deck of cards with files attached to another server. Exporting the cards using occ deck:export works but all attachments are lost. This is also the case when exporting using the REST API. Analysing the database shows that the table oc_deck_attachment is empty. But both in the Web Browser and in the Android app the attachments are shown and can be read. The're also in the Deck folder in Nextcloud - but I cannot find any link I could migrate manually.
What is going on here? Where does the Deck application connects its attachment with the cards and the files in the file system? Not in the database - but not in the file system either. I know of the different versions of the linking - but cannot find any proper documentation.
How can I migrate my data?
Source version: 32.0.3
Destination: 33.0
Thank you very much.
Conrad
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 by tracing occ deck:export and the REST API attachment handling, then compare those paths with the oc_deck_attachment table and the Deck folder mentioned in the report. Check how the source version 32.0.3 and destination version 33.0 represent attachment links. Done means identifying the attachment relationship and establishing a migration path that preserves exported attachments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100