This is by design. The Bulk Optimizer for the Media Library does not prevent duplicate optimization, because it only ever needs to run once. The intent is that you can modify your optimization settings later, and re-run the Bulk Optimizer if you want to apply those settings to previous images. All new images are auto-optimized, so there is never a need to re-run it unless you have changed your settings.
In that case it would be best if the Bulk Optimizer should state this. It would be most clear if it will differentiate between these two states and communicate that to user.
All images have already been optimized. If you have changed your _optimization settings_, you can optimize all images again here.
Newly added images will be automatically optimized.
[Optimize Again]
vs.
Newly added images will be automatically optimized. However, there are some older images that have not yet been optimized.
[Optimize Images]
This is another area where I’m re-evaluating some design decisions, partly due to cloud users where they may not want it to re-optimize, even for the Media Library. If I merge the two optimization tools, I can also simplify things by making the both tools behave similarly. For Bulk Optimize this may actually be quite easy, since we already store some metadata for all Media Library items.
Somewhere in there, we can just have a checkbox or perhaps a separate button that allows the user to re-optimize in the bulk tool. Hmm, lots of food for thought here.
