Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloading attachments generates generic filenames #854

Open
5 tasks done
Spreadcat opened this issue Mar 16, 2024 · 1 comment
Open
5 tasks done

Downloading attachments generates generic filenames #854

Spreadcat opened this issue Mar 16, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Spreadcat
Copy link
Contributor

Spreadcat commented Mar 16, 2024

First Check

  • This is not a feature request
  • I added a very descriptive title to this issue.
  • I used the GitHub search to find a similar issue and didn't find it.
  • I searched the documentation, with the integrated search.
  • I already read the docs and didn't find an answer.

Homebox Version

0041c27

What is the issue you are experiencing?

After uploading either a PDF document or an *.xlsx file hombox shows the correct name for the attachment.
When trying to save the file, the following happens

  • PDF documents are pre-named document in the file-save dialog (probably the same when auto-downloading).
  • XLSX documents are receiving a hash-like filename in the file-save dialog.

How can the maintainer reproduce the issue?

  1. Upload a PDF document of any kind to an asset/item and save the item.
  2. Click on the "download" button in the attachment section to initiate the download.
  3. When the file-download dialog opens and asks for the location of there to store the file, the pre-filled document name has changed to document instead of the original filename.

Deployment

Docker (Linux)

Deployment Details

No response

@Spreadcat Spreadcat added the bug Something isn't working label Mar 16, 2024
@danielrosehill
Copy link

I've noticed that for images the system will also autogenerate titles based on the renamed files. This makes it very difficult to manage the photographs associated with an asset (for instance if I want to delete a specific picture, it's impossible to know what the path is).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants