WordPress.org

Support

Support » Plugins and Hacks » autoptimize 1.8.x: problems and how to solve them

autoptimize 1.8.x: problems and how to solve them

Viewing 15 replies - 1 through 15 (of 27 total)
  • Plugin Author Frank Goossens
    Participant

    @futtta

    There is a bug in 1.8 which results in CSS in conditional comments (“iehacks”) not being excluded, more info here.

    If the fix is confirmed, I’ll push out 1.8.1 in the following hours. Sorry for the inconvenience!

    Plugin Author Frank Goossens
    Participant

    @futtta

    update; 1.8.1 was released just now, conditional comments are excluded from autoptimization again.

    Plugin Author Frank Goossens
    Participant

    @futtta

    In some cases (e.g. when using Dynamic to Top) a conflict of CSS minfiers causes “white screens of death”. Disabling CSS optimization in Autoptimize or disabling the plugin that has the conflicting CSS minifier will fix this. 1.8.2 (due 2nd half of february) will have a fix for this.

    Hi, I got 500 internal server error after using this plugin. Please give me a solution.

    Plugin Author Frank Goossens
    Participant

    @futtta

    Hi Sata2z;
    Do you have the 500 on the backend (/wp-admin/… but that is unlikely) or on the frontend of the blog? If on the frontend: disable all optimization (HTML, CSS and JS) and then try them one by one to identify the one which is causing the error. Once you have that, you should be able to activate the other ones.

    The rootcause most probably is another plugin which is also doing CSS and or JS optimization (e.g. “dynamic to top” as mentoined earlier or W3 Total Cache CSS/JS optimization). Disabling other plugins while having Autoptimize fully active (for HTML/ CSS/ JS) could help you identify which plugin is not compatible. If you have that, I can look into what is going wrong and if I can solve this.

    Hope this helps,
    frank

    Hi Frank thanks for your quick response. I deleted W3 Total Cache in my plugin list. And i disable css and js check box, now running page correctly. But page speed is still same.

    Plugin Author Frank Goossens
    Participant

    @futtta

    Well, you don’t have to delete W3TC, just make sure it doesn’t do CSS/JS optimization. Do you have the white screen when enabling just CSS and also when enabling just JS?

    Yes, if i enable CSS the white screen with error displaying. And if i enable JS my website other popup’s are not working.

    Plugin Author Frank Goossens
    Participant

    @futtta

    For the JS-part; you need to configure it, I advise you to read the FAQ for that.

    For the CSS-part; what other plugins are you using? What theme? What do you see in your PHP-error-log?

    ********plugins list********
    Appointy – Appointment Scheduler, Automatic Sign Out For Inactivity, Contact Form 7, Email Log, Email newsletter, Events Manager Pro, JE Alert, JE Coupon, JE Custom Fields, JE LinkedIn, JE Paypal Express, jQuery Mega Menu, Widget Logic, Widgets on Pages, WordPress Ad Widget, WP News Bulletin

    *****Theme name****
    http://demo.enginethemes.com/jobengine-preview/

    where i can find PHP-error-log, please advice?

    Plugin Author Frank Goossens
    Participant

    @futtta

    For the location of your PHP-error-log you should check with your hoster. The info in there will probably be very relevant, so it is probably very worth while to look into it.

    Regarding the plugins; if possible it would help to briefly disable all plugins but Autoptimize and see if CSS optimization still triggers the white page. If not, the problem is with a plugin, if yes the problem is with the theme (which you can also confirm by briefly switching themes).

    Plugin Author Frank Goossens
    Participant

    @futtta

    For those who encounter problems, a first version of what will become 1.8.2 has just been pushed to http://downloads.wordpress.org/plugin/autoptimize.zip.

    Some of the improvements/ fixes included;

    • deferred CSS added in noscript-tags
    • check for availability of method on minifier class before invoking it (yet another white screen of death being offed)
    • improvements in CSS import code

    Feel free to download and provide feedback here!

    Just downloaded the dev version, trying to make deferred css work with

    <!--noptimize-->
    <style>body { background: #eaeaea; }
    </style>
    <!--/noptimize-->

    the above part is not loaded… Did I miss how this is supposed to work? As I figured it, the point would be to load the essential css inline like above and deferr the rest. So I included that and enabled the deferr css option.

    Is it supposed to be done differently? Thanks for all your work 🙂

    Plugin Author Frank Goossens
    Participant

    @futtta

    Evening LuxDelux;

    body { background-color: #eaeaea; }

    might be better? if you put that in between the noptimize-tags as shown in your example (and style-tags, off course) that indeed should work (i.e. the CSS should be inline instead of aggregated in the autoptimize_*.css file).

    hope that helps,
    frank

    Sorry, I didn’t explain my problem clear enough:

    – the inline css is in the head with noptimize-tags
    – the “Defer CSS loading?” option is checked

    the css files are deferred but the inline part is not loaded by the browser. I can see it in the code but the styles aren’t applied to the elements. It loads when “Defer CSS loading?” is not checked but that doesn’t bring much load improvement (per your website post I had the idea to deferr everything except critical parts)

    I tried switching the inline part around (before and after wp_head()) but nothing seems to make a difference.

    Any ideas? Or is this functionality not yet implemented?

    Cheers

Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘autoptimize 1.8.x: problems and how to solve them’ is closed to new replies.