Autoptimize 2.4: known issues, workarounds and next minor version
-
So the dust seems to be settling after a rather hectic couple of days following the release of AO 2.4 ??
These are the known issues;
* long time to first byte; on some servers (without support for mbstring, a minority luckily) Autoptimize fell back to using iconv_substr for multibyte character conversion, which slowed things down considerably. this will be fixed in 2.4.1 (which by default won’t use iconv any more)
* high CPU usage; I saw 2 mentions of this, but have not received details. this might very well be the same as the previous issue though and if so will also be fixed in 2.4.1.
* HTTP 500/ blank pages; it turned out that the new (much faster) version of the CSS minifier that AO uses expects somewhat better CSS. in case of syntax errors in the CSS, the minifier crashes. I will add an item in the FAQ to warn users about this.
* In some cases not all Google Fonts were loaded due to a missing & in the aggregated Google Font CSS, this will be fixed in AO 2.4.1.
* In one case the CSS minifier replacedblack
in a font-family name with#000
which resulted in the font not being applied, I’ve opened an issue on the minifiers’s github page.
* if minification was disabled with a filter (which is very exceptional), some CSS/ JS got lost, this will be fixed in 2.4.1.
* one report of excluded JS breaking because of minification, this can be worked around with a simple code snippet (it’s mentioned in the AO FAQ). I might turn this into an option on the settings-screen at a later stage.That’s it for now, 2.4.1 will probably be released shortly after Oct. 1st.
Enjoy the weekend! ??
- The topic ‘Autoptimize 2.4: known issues, workarounds and next minor version’ is closed to new replies.