Not case sensisitve

Hello Dan,

I rename to .jpg only if the whole filename is changing as well. The reason is that on a few systems it will not work, .JPG = .jpg. You can’t rename a file to the same name. Basically that happens on Windows and that would end on a WordPress that is not really synchronized between its DB and filesystem and the day you migrate to another system it will be really broken and hard to repair.

If you want to force it, you can simply search and replace the occurences of “strtolower” to “” (nothing) in the whole code. There are probably two occurences. Let me know what it does and if it works for you… But to be honest, this is just a visual thing (JPG or jpg is the same from a technical or SEO point of view) so it’s better to keep things working and safe first.

It’s not a problem or a matter of SEO concerns — I just wanted to note it and see if it’s known/intentional.

The situation is exactly as you describe — the file system has a number of .JPG files that are .jpg in the database, and the *nix environment treats them as different. This is easily fixed from the command line.

I thought the plugin might work as you describe and change the extensions to lowercase if I changed the rest of the filename, but I tried that and the capital .JPG still remained.

Yes, I keep it this way to avoid problem. I actually gave a solution in another thread on this forum recently to force the plugin to do it anyway (basically by simply removing the two strtolower in the code). The only issue is that you might encounter issue one day in the future so I’d rather do the check, and the plugin doesn’t do this in this specific case. Better to be safe than sorry and honestly renaming a JPG to jpg is only to appeal to our eyes (and I doubt the visitors care). That’s why I keep it this way. You can can try to remove the strtolower if you like.