I’ve got an eForm with file upload (the file is uploaded just fine and can be accessed via ftp), and the report uses
<a href="http://www.domain.com/assets/files/uploads/[+filename+]">[+filename+]</a><br />
to generate a link in the email for downloading the file. The problem is that somewhere along the line the filename is getting URL encoded if it has special characters (specifically ü) and this is breaking the link resulting in a 404 (and of course it’s not an option to tell everybody not to use these in filenames
).
I can’t figure out where the encoding is taking place.
Can anybody give some advice on how I might deal with this?
The email link method is specifically required (there are quite a few absurdities in the whole process) so I can’t use some other method of making the uploaded files available.
Interestingly enough, after reading through the posts about the file manager urlencoding issues, I find that I also cannot download this file from the file manger, although I’m using 0.9.6.2 (I know; the client refuses to consider an upgrade). In fact, I can’t even download the file if I manually enter the filename in the browser address bar! Windows server, and a .doc file, by the way.
☆ A M B ☆
