@bobsled Hi Bob, I believe you are a long time user of the plugin? 🙂 Hang in there! The next update will address this issue. Most likely with you this week.
Okay, I’ll wait and see if you can fix the issue.
But in the meantime, I have rolled back to version 1.5.9 and everything is fine.
But please, please, test your plugin before you rush to update. This is an issue that really should have been caught in your testing.
-
This reply was modified 2 years, 6 months ago by bobsled.
@bobsled
Please update to version 2.0.2. The unused CSS has been reduced dramatically.
Thanks for letting me know @van-ons
I just did a very quick check and yes, there is a dramatic drop in unused CSS. It’s now down to about the same as version 1.5.9.
I’ll do a bit more testing shortly, but it certainly looks like all is well now.
I’ve updated two live sites to 2.0.2, @van-ons
Both show a small increase in unused CSS of about 38,000 bytes over version 1.5.9.
So it’s not too bad, but it would be better if you could trim a little more of the CSS fat, if possible.
I tried updating my main site and it had the same CSS bloat problem. It increased my used and unused CSS by an enormous amount. I have rolled back again to 1.5.9 and the CSS bloat is gone.
I’ll give you some time to sort it out. But I’ll have to find an alternative solution if this problem persists.
I’m sorry, but I have run out of patience with the new version of this plugin. I’ve now found a better alternative.
It’s such a shame because I have used it for well over three years without any issues.
But taking over a popular plugin and releasing a totally new version as an update is always a recipe for disaster. It’s usually untested and full of bugs.
In this case, the new version added huge amounts of bloat. My Autoptimize cache jumped from 5MB to over 35MB. The unused CSS increased six-fold or more.
And it’s not the responsibility of users to patiently debug a new plugin.
I have wasted at least 10 days on this plugin. That’s more than enough.
I just don’t understand why a developer would take over a perfectly good and very popular plugin and then ruin it.
Yes, the new developer wants to promote a premium version and make some money.
But this can just as easily be done by updating the perfectly good original plugin incrementally.
@bobsled
This issue has been fixed in 2.0.3. Please update to the latest version 🙂