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?
to your account
Another instance of an error is if there's an apostrophe in the file name of a deposited file, then we get this:
To reproduce the error, upload a file with an apostrophe in the name, for example:
We need to escape any apostrophes in the copy calls.
The text was updated successfully, but these errors were encountered:
Investigating this further, testing with the file 'collectivités_traumatisé's.pdf'
the copy operation fails on this line:
The error is caught, but the details are not displayed, tracing the error, the details are actually:
Copy failed: No such file or directory*
It fails because the file is not found.
The file is not found because when I look at what is actually stored in that location on disk, it is this:
So does EPrints substitute apostrophes in file names with "=0027" when it saves them to disk?
Sorry, something went wrong.
Fix for issue: #40
regex to catch the apostrophe in filename transformation on disk
improved error handling to provide more details on the error in the log
added a regex to catch this transformation of filename on disk, and more details on the error log if/when copy operation fails again. this resolved the issue on my repository.
will include this fix in next release 1.2.3
The double-apostrophe causes the same failure.
To reproduce, deposit a file with this filename: As"ad.pdf
On disk, the " is replaced by =0022
Expanded fix for Issue #40 dealing with a double-quote
Another special character that gets replaced, in addition to quote, double-quote, colon.
So we have this:
replacing any : in a filename.
Need to include that in the REGEX.
Exand fix for issue with some characters getting replaced in the file…
…name, addition of colon to the fix for: #40
Add colon to regex in fix for Issue: #40
No branches or pull requests