Sounds like some plugin is mucking with the script loading on the backend, and eio.js is not able to load properly as a result. I would recommend disabling all plugins, and then re-enabling them one at a time to find the one that breaks it (unless you can figure it out without doing that).
Once you’ve figured that out, see if the plugin has an option to disable script mangling on the wp_admin.
EDIT: I suppose it COULD be your theme doing that also, but I hope not…
How important is running the “Optimize Everything Else” option. Will it make a big difference in performance?
Depends on what you are using it for. If it is only for theme images, you can just turn on Scheduled Optimization (advanced settings), and it will take care of it in the background. If you want it to scan some huge folder, then obviously that would be more important.
Most folks who run it are using it for their theme, or they’ve found some group of images generated by a plugin that doesn’t get optimized by the normal bulk optimize, so they want it to do a specific folder(s).
Sounds good, thanks for your help and tips 🙂
I think I am having the exact problem that kb959fl posted here, and would like to resolve it if possible.
I followed the steps you outlined above, nosilver4u. I first made the change to ewww-image-optimizer.php, then turned on debug, and then let the “Optimize Everything Else” run for a few minutes. This is the resulting debug log file: http://pastebin.com/siSGQ0y6
After that, I turned off debug mode and then went back to the Bulk Optimize page, enabled JavaScript Console in Chrome, and started the “Optimize Everything Else” process again. Within a couple of seconds, I got this error in JavaScript Console: http://pastebin.com/5HUb0ejD
I disabled ALL plugins except EWWW, and returned to the Bulk Optimize page and repeated the above, but got the exact same error even with all plugins disabled.
Do you have any thoughts on this or a troubleshooting direction I should head next? Thanks for your help.
That’s actually a known bug. It “should” mean that there are no images left to optimize in the folders specified. There are some big improvements coming to the Scan & Optimize in the next release (plus fixing that bug).
