can you send me a link to the file in question?
After uploading it to my server, I’ve verified what I suspected. The fault is not with the plugin, it is actually native to wordpress (the GD library used to generate thumbs more precisely). I believe it has difficulty with 8-bit PNGS, usually that is in relation to transparency, but perhaps the difficulty is that wordpress never bothers to check if a PNG is 8-bit, and just mangles all the thumbs to 24-bit regardless.
Unfortunately, it doesn’t appear that either optipng or pngout attempt to downsize them back to 8-bit, so you’ll want to see if you can find some utility to take care of that for you. pngout is able to save some extra space if you crank it to the lowest setting, but unless you’re on a dedicated server, I would avoid that. optipng only manages to scrape off 2 bytes at max settings, so that’s not worth much. Both of them fully support 8-bit PNGs in my testing, so that fully confirms that the blame lies with the GD library that does the resizing.
I’ll take a look at the ftp uploading issue here in a bit.
ok, I think I misunderstood your other issue. Is it the same file that gives you the ‘unsupported file type’ message?
My suspicion is that while the EWWW IO plugin is enabled, the png optimization takes so long (because of that massive 1.4 MB PNG resize that wordpress creates), that some of the metadata is corrupted or not generated when you upload it. The file could very easily be uploaded, and show up via your FTP, but not properly registered in the database, since the optimization is done during the metadata generation process. There’s not really any way around that, sorry.
Thanks for your attention, nosilver4u. Yes this is the same file. So I need to optimize it manually, of course it’s pity, but anyway thanks!
