-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Description
Sometimes when uploading a file, the type of the file is set to the type that was appropriate for the previous upload performed by that user, rather than what is suitable for this folder.
Unfortunately, I don't have the exact steps needed for a reproduction scenario, but I've seen this bug happen often enough that I feel I should document it here.
Incomplete reproduction steps
- User navigates to a folder that has allowed types configured to contain exactly 1 value, e.g.
acme:commonDocument - User uploads a file, gets prompted with a metadata panel and fills it out. The file is automatically converted to type
acme:commonDocument - User navigates to a different folder that does not have allowed types configured
- The call to
uploader-plus/allowed-content-types?destination=…returns{ "types" : null }
- The call to
- User uploads a file and is not prompted with a metadata panel
Expected behaviour
The uploaded file is of type cm:content
Observed behaviour
The uploaded file is of type acme:commonDocument
Metadata
Metadata
Assignees
Labels
No labels