-
Notifications
You must be signed in to change notification settings - Fork 26
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
.msg files cannot be uploaded #4795
Labels
Comments
LaurensBurger
added
bug
Something isn't working
triage
Issue needs to be validated. Remove this label if the issue considered valid.
labels
Oct 25, 2024
Resembles #4773 |
joeribekker
removed
the
triage
Issue needs to be validated. Remove this label if the issue considered valid.
label
Oct 28, 2024
I'll provide a .msg file |
robinmolen
added a commit
that referenced
this issue
Dec 19, 2024
robinmolen
added a commit
that referenced
this issue
Dec 19, 2024
robinmolen
added a commit
that referenced
this issue
Dec 19, 2024
robinmolen
added a commit
that referenced
this issue
Dec 19, 2024
The sdk cannot determine which content type belongs to a .msg file. This is because (at least) Linux and MacOS don't know this file type. To make sure these files can be uploaded, the type property on the FileSerializer is now optional. For .smg files a new rule has been added to the MimeTypeValidator
10 tasks
robinmolen
added a commit
that referenced
this issue
Dec 19, 2024
robinmolen
added a commit
that referenced
this issue
Dec 23, 2024
The sdk cannot determine which content type belongs to a .msg file. This is because (at least) Linux and MacOS don't know this file type. To make sure these files can be uploaded, the type property on the FileSerializer is now optional. For .smg files a new rule has been added to the MimeTypeValidator
robinmolen
added a commit
that referenced
this issue
Dec 23, 2024
robinmolen
added a commit
that referenced
this issue
Dec 23, 2024
robinmolen
added a commit
that referenced
this issue
Dec 23, 2024
The sdk cannot determine which content type belongs to a .msg file. This is because (at least) Linux and MacOS don't know this file type. To make sure these files can be uploaded, the type property on the FileSerializer is now optional. For .smg files a new rule has been added to the MimeTypeValidator
robinmolen
added a commit
that referenced
this issue
Dec 23, 2024
robinmolen
added a commit
that referenced
this issue
Dec 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Product versie / Product version
tested on 2.7.x 2.8.x
Customer reference
Utr 306
Omschrijf het probleem / Describe the bug
Sentry: 313314
When uploading a .msg file and after navigating to the next step the upload component shows a error:
ValidationError {'data': {'bestandsupload': {0: {'type': [ErrorDetail(string="Het bestandstype kon niet bepaald worden. Controleer of de bestandsnaam met een extensie eindigt (bijvoorbeel '.pdf' of '.png').", code='blank')]}}}}
Tested with multiple OSes, and multiple files and environments.
The text was updated successfully, but these errors were encountered: