Alex Dunae

It does work on thumbnails (and all generated sizes) even if the original is too big, it just doesn’t report it. I should find a way to indicate that.

According to the Smush.it site all that data should still be there. Isn’t it?

It should work just fine. I’m running it on 3.5.1 with no problems.

Fixed in the next release. Sorry about that.

The next release will have an option to set the timeout higher as well as some more forgiving errors when an image can’t be smushed.

That said, most of the speed bottleneck comes from the Smush.it servers. There’s nothing we can do about that, unfortunately.

Not sure what you mean — WP Smush.it (the plugin) will process all the sizes WordPress generates. The actual Smush.it API only returns a single image; all the versions they create when experimenting are kept on their server, inaccessible to the public.

Looks like the plugin is having issues with Windows paths (vs. Mac or Linux). I’ll take a look.

That said, the plugin won’t work on your localhost. It needs to be on a publicly-available server.

Fixed in the next release. Thanks for reporting this.

Awsome, thanks kindly for the patch. I’ve applied it in trunk and it will be part of the next release.

The image size thing is (unfortunately) a limit of the Smush.it server.

The next release will have a bit more graceful error handling.

There isn’t currently, though it will handle a non-standard wp-content directory. What’s the use case you have in mind?

Unfortunately you’re right – it’s just a limitation of the Smush.it service. I wish it was otherwise…

Unfortunately that’s just a limitation of the Smush.it service. Definitely unfortunate, I know.

That’s great, thanks muchly for your kind words.

There’s already been a bit of interest in people taking it over, so hopefully the smushing can continue!

@zepolo not compatible in what way? Did you get an error?