-
Notifications
You must be signed in to change notification settings - Fork 174
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
[media] Downloading file with special characters in name leads to error: Failed - no file #6136
Labels
Category: Bug
PR or issue that aims to report or fix a bug
Comments
There's a chance that this affects other modules with file download capabilities too. |
This was referenced Mar 17, 2020
laemtl
pushed a commit
to laemtl/Loris
that referenced
this issue
Jun 2, 2020
This aims to fix a bug that was experienced by a CCNA user when trying to download a file that had a '&' in the name. SQL encodes strings containing special chars and thus we need to use the decoded file names in the path when downloading files from media module. Resolves aces#6136
laemtl
pushed a commit
to laemtl/Loris
that referenced
this issue
Jun 2, 2020
This aims to fix a bug that was experienced by a CCNA user when trying to download a file that had a '&' in the name. SQL encodes strings containing special chars and thus we need to use the decoded file names in the path when downloading files from media module. Resolves aces#6136
laemtl
pushed a commit
to laemtl/Loris
that referenced
this issue
Jun 11, 2020
This aims to fix a bug that was experienced by a CCNA user when trying to download a file that had a '&' in the name. SQL encodes strings containing special chars and thus we need to use the decoded file names in the path when downloading files from media module. Resolves aces#6136
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There is an error when downloading files from media module that contain special characters in its name (ex: '&'). Error message that appears says "Failed - No File". This is likely occurring because SQL changes such characters to their html encoding.
To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):
What did you expect to happen?
File should download normally.
Browser Environment (please complete the following information):
Server Environment (if known):
Note: We only support the most recent release of LORIS.
The text was updated successfully, but these errors were encountered: