Skip to content

Documents uploaded with Mime Type = application/octet-stream always #28

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

Closed
denikqwerty opened this issue Sep 7, 2023 · 5 comments
Closed

Comments

@denikqwerty
Copy link

When using your extension we realized that when we upload a file via Drag and Drop area it is actually uploaded with mimetype = application/octet-stream while if we upload the file via normal attachment, it is uplaoded with actual file mime type, like application/pdf, image/jpeg etc.

Can you please fix that? It is critical for us

@RubenAghajanyan
Copy link

@denikqwerty

But, files are uploading with their mime-type. You can upload a file via control, download it from notes, and check its mime-type. https://www.htmlstrip.com/mime-file-type-checker
It will show the correct mime-type.

Can you please share more info, how did you find out that mime-type sets application/octet-stream?

@denikqwerty
Copy link
Author

denikqwerty commented Sep 12, 2023

@RubenAghajanyan

We`ve uploaded one and the same pdf to the records where we have Drag and Drop Area enabled, and as you can see mime types of them are different.

1st row represented note attached via Drag and Drop area
2nd row represents note attached via OOB process

image

Please tell me if you need more information. You need to check mime type not of downloaded file, but the annotation record itself, like:

<fetch>
  <entity name="annotation">
    <attribute name="objectid" />
    <attribute name="filename" />
    <attribute name="mimetype" />
    <filter>
      <condition attribute="isdocument" operator="eq" value="1" />
      <condition attribute="objectid" operator="eq" value="[id of your record]" />
    </filter>
  </entity>
</fetch>

@RubenAghajanyan
Copy link

@denikqwerty,

Okey. We published a new version "1.0.2" where that bug should be fixed. Please download it from the marketplace
https://marketplace.bevercrm.com/pcf-controls/1

@denikqwerty
Copy link
Author

@RubenAghajanyan Thank you very much for the quick fix. The issue is resoved :)

@RubenAghajanyan
Copy link

The issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants