Hi there,
Often users attempt to upload images with spaces in their filename.
The database stores the image exactly as it is named on the user system.
However, Linksql stores the image on the server with spaces converted to %20;
When I attempt to access the filename based on the data found in Links_Files.
The system attempts to call a file named:
"http://mydomain.com/somefilename withspace.jpg"
instead of:
http://mydomain.com/...name%20withspace.jpg
But even that won't work because since the filename is coded with %20, we can't request
http://mydomain.com/...name%20withspace.jpg
instead we have to request:
http://mydomain.com/somefilename%2520withspace.jpg
because %20 means space and %2520 means %20
Where would we fix this in 2.1.2
Can this be fixed in the next release?
Wouldn't it be easiest to convert all funky characters to _ and save the file and filename to the server accordingly as is done when creating directory names?
Thank you in advance for any suggestions on fixing this.
peace.
klangan
Often users attempt to upload images with spaces in their filename.
The database stores the image exactly as it is named on the user system.
However, Linksql stores the image on the server with spaces converted to %20;
When I attempt to access the filename based on the data found in Links_Files.
The system attempts to call a file named:
"http://mydomain.com/somefilename withspace.jpg"
instead of:
http://mydomain.com/...name%20withspace.jpg
But even that won't work because since the filename is coded with %20, we can't request
http://mydomain.com/...name%20withspace.jpg
instead we have to request:
http://mydomain.com/somefilename%2520withspace.jpg
because %20 means space and %2520 means %20
Where would we fix this in 2.1.2
Can this be fixed in the next release?
Wouldn't it be easiest to convert all funky characters to _ and save the file and filename to the server accordingly as is done when creating directory names?
Thank you in advance for any suggestions on fixing this.
peace.
klangan