Support » Plugin: Autoptimize » Autoptimize 2.4: known issues, workarounds and next minor version

  • ResolvedPlugin Author Optimizing Matters

    (@optimizingmatters)


    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 replaced black 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! 🙂

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    for anyone experiencing these issues; if you want you can try out the beta by downloading it from https://github.com/futtta/autoptimize/archive/beta.zip 🙂

    The beta version of the plugin 2.4. did not help for me.

    The plugin 2.4. incorrectly displays js and css in the end. Right inside the </html> tag, for example:

    </<script type=”text/javascript” defer src=”https://narcofree.ru/neNa1dESh/wp-content/cache/autoptimize/js/autoptimize_11be328757dc281af7c5758e335e7c3b.js”></script></<script data-cfasync=’false’>!function(t){“use strict”;t.loadCSS||(t.loadCSS=function(){});var e=loadCSS.relpreload={};if(e.support=function(){var e;try{e=t.document.createElement(“link”).relList.supports(“preload”)}catch(t){e=!1}return function(){return e}}(),e.bindMediaToggle=function(t){function e(){t.media=a}var a=t.media||”all”;t.addEventListener?t.addEventListener(“load”,e):t.attachEvent&&t.attachEvent(“onload”,e),setTimeout(function(){t.rel=”stylesheet”,t.media=”only x”}),setTimeout(e,3e3)},e.poly=function(){if(!e.support())for(var a=t.document.getElementsByTagName(“link”),n=0;n<a.length;n++){var o=a[n];”preload”!==o.rel||”style”!==o.getAttribute(“as”)||o.getAttribute(“data-loadcss”)||(o.setAttribute(“data-loadcss”,!0),e.bindMediaToggle(o))}},!e.support()){e.poly();var a=t.setInterval(e.poly,500);t.addEventListener?t.addEventListener(“load”,function(){e.poly(),t.clearInterval(a)}):t.attachEvent&&t.attachEvent(“onload”,function(){e.poly(),t.clearInterval(a)})}”undefined”!=typeof exports?exports.loadCSS=loadCSS:t.loadCSS=loadCSS}(“undefined”!=typeof global?global:this);</script></body>tml>

    The plugin 2.3.4. correctly displays this, before the closing html tag.

    If I checkmark “Optimize CSS code” – it kills my website and screen is completely blank. If I uncheck it, then everything works, but my page-loading time increased…

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    @igb10; that’s because of “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.”, you very likely have a closing bracket missing somewhere.

    @rexmid; only saw your message just now, do you have a non-live site where we could look into that?

    I don’t have my site non-live, it’s wordpress sitting on the server. If any brackets weren’t closed, something wouldn’t work properly. I also successfully validated CSS at W3C without any issues.

    I have to say I just moved my website from Windows server with PHP 5.4 to Linux servers with PHP 7.2. Everything worked fine on IIS, but I think if was a coincidence that at the same time this plugin was updated when I moved. However I didn’t move plugin from my old host, I just did a fresh install on the new server. My website is mbzmaster.com

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    @igb10; had my quick look and I can confirm your CSS is perfect, so the next steps:
    1. have a look in your php errorlog for relevant errors
    2. try with option “also aggregate inline CSS” off
    3. if (2) still results in errors, then try to exclude the linked stylesheets (wp-content/themes/twentyseventeen/style.css, wp-content/themes/mychildtheme/style.css, wp-content/plugins/add-to-any/addtoany.min.css) one by one to see which one causes the crash

    frank

    If I check-mark “Optimize CSS Code?”, but uncheck “Aggregate CSS-files?” then website works. But as soon as I check both – I get blank page.
    I also tried to disable AddToAny plugin, but again if I check both – I get blank page even with addToAny disabled completely.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    have you (and if not can you) check what happens when excluding the CSS if the child or the parent theme from optimization and (even more important) can you check your PHP errorlog for errors?

    I really don’t have time to deal with PHP errors enabling and figuring how to disable external files. Is there any way to roll back AO to the previous version? Because I haven’t had any problems before..
    Or maybe I’ll just wait for the new AO version release and then try to enable it again.
    But thank you for trying to help anyway.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    sure, you can roll back by downloading 2.3.4 here and installing that @ibg10 🙂

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    2.4.1 was just released 🙂

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Autoptimize 2.4: known issues, workarounds and next minor version’ is closed to new replies.