I found many times the PunyPNG and Smushit websites either timed out or returned 500 errors. While I realize this is not the tool's fault, it does limit the usefulness.
In addition, while working with Assembla as a code repository, it will often delete images that do not need optimizing. Those that were optimized are saved properly. Can't seem to see a pattern, but once again this really limits the usefulness. If you optimize a folder, you have to figure out what images are deleted that should not have been from others that were optimized.
looks nice but it seems it screws up my positioning of team explorer and other stuff.. I constantly have to move the windows to what I'm used to. Once uninstalled the problem stopped?
Anyone else with this problem?
@Mads Kristensen (oddly I didn't find a way to reply.. maybe I overlooked it :) ) The Team Foundation window, pending changes,... did a new install and now it's working fine.. must have been a Visual Studio hiccup :)
This is probably because you're image files are under source control. Check them out first and then run Image Optimizer. I'm working on an update that will check out the files from source control automatically
this toll is awesome. They save me a lot of time.
But unfortunately today it just stop working
I tried remove and install again, restart VS but noting help. Pls tell me if someone have solution for this problem.
Message which I got:
------ Image optimization started -----
The remote name could not be resolved: 'smushit.eperf.vip.ac4.yahoo.com'
D:\Current\images\ActivationInstructions01.png - using http://smushit.com
1 skipped. 0 optimized. Total savings 0%
------ Image optimization finished -----
Works great, but having an issue that the optimiazation adds some artifacts for some png images that I dont want. (background images with solid colors changing from dark to light grey)
Can I prevent it from optimizing a few images in the solution?
I am having this same issue ("An exception occurred during a WebClient request"), but I don't believe it is a firewall problem. I watched the request/response in Fiddler, and it very clearly gets a response of 200 with a JSON object in the payload describing how much the image was "smushed" and where the new image resides. I don't see a follow-up request that actually retrieves the smushed image, though, so I'm guessing this is where the error is occurring. Any ideas?