JFn Posted November 27, 2019 Share Posted November 27, 2019 Since most Operating systems support unicode file names, I'm wondering why PW still sanitizes (image) filenames to [-_.a-z0-9] characters only. I've used @adrian's Custom Upload Names module before to change file names, but it still depends on @ryan's core Pagefiles->cleanBasename, which strips out all non ascii characters. HDPI images are often named "image@2x.jpg" and from a copyright perspective "image©2019-company.jpg" would be far more practical (obvious) than hidden exim data. Something like "image-ab&cd.jpg" or "image(v2).jpg" isn't a weird thing either. Linux, Windows and MacOS can all handle this kind of file names, and offcourse modern browsers too. Is there any particular reason why this couldn't be implemented as a default in PW? 1 Link to comment Share on other sites More sharing options...
adrian Posted November 27, 2019 Share Posted November 27, 2019 Not terribly helpful, but here is an old discussion about this: Link to comment Share on other sites More sharing options...
adrian Posted April 2, 2021 Share Posted April 2, 2021 Just out of interest, I recently removed cleanBasename from Custom Upload Names because it was doing weird things with filenames. It's much better without it ? Link to comment Share on other sites More sharing options...
TheMick Posted September 6, 2021 Share Posted September 6, 2021 @ryan Does ist still make sense to have such a restrictive function for filenames? Link to comment Share on other sites More sharing options...
Recommended Posts