You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tested this on 2 projects and made a GET call to see what the PDF would return.
Migrated project returns: "mediaTypeAlias": "File"
New project returns: "mediaTypeAlias": "umbracoMediaArticle"
That is cause from what I can see none of the migrated projects received the additional media types such as article, audio etc.
Either way, uploading the PDF doesn't work whether I input File or umbracoMediaArticle in the call.
I've also confirmed that the extension .pdf isn't disallowed in the uploadFile field.
It is, however, possible to upload a PDF by using this format:
The problem with this is that the PDF ends up like this:
Using any of the others media type aliases in the mediaTypeAlias results in the call creating a media container but not uploading the actual file into it like so:
The text was updated successfully, but these errors were encountered:
Issue description
I get a 422 response when trying to upload a PDF
Here's the cURL:
I've tested this on 2 projects and made a GET call to see what the PDF would return.
Migrated project returns:
"mediaTypeAlias": "File"
New project returns:
"mediaTypeAlias": "umbracoMediaArticle"
That is cause from what I can see none of the migrated projects received the additional media types such as article, audio etc.
Either way, uploading the PDF doesn't work whether I input
File
orumbracoMediaArticle
in the call.I've also confirmed that the extension .pdf isn't disallowed in the uploadFile field.
It is, however, possible to upload a PDF by using this format:
The problem with this is that the PDF ends up like this:
Using any of the others media type aliases in the
mediaTypeAlias
results in the call creating a media container but not uploading the actual file into it like so:The text was updated successfully, but these errors were encountered: