Box “Don’t optimize for logged in users” doesn’t work

  • Resolved Marie0638

    (@marie0638)


    7 years, 7 months ago

    Hello,

    I’ve upgraded to the newest version Autoptimize. When I checked my pages, I’ve discovered Visual Composer wasn’t working anymore.

    I see on FAQ that you advice to use the box “Don’t optimize for logged in users”. For me, checked or unchecked, it doesn’t solve the issue.

    So I’ve tried to get back to the older version (nothing changed except that), but the issue remains even though it worked before…

    Any idea ? Because I really need VC and if I can’t make it works, I will be forced to desactivate your plugin (and I’m happy with it, except this issue !).

    Thanks for your help.

    Wordpress : last version (4.8.1)
    Autoptimize : last version (2.2.2)
    Scripts excluded : seal.js, js/jquery/jquery.js

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

    (@optimizingmatters)

    Hmm … Do you have a page cache that is getting in the way maybe?

    Thread Starter Marie0638

    (@marie0638)

    I use also WP Fastest Cache and Async Javascript.

    After some tests, it seems odd !

    I cleared my theme cache and plugin cache (after all steps mentionned below) : when I desactivate Autoptimize, VC appears on some pages and not on others (test based on 3 different pages).

    When I reactivate AO and desactivate Async JS, VC perform the same way (on same pages).

    When I have AO and Async JS activated, and I desactivate WP Fastest Cache, VC disappears on some pages that worked before (but it works on others).

    Finally, when desactivating 2 plugins (Async JS + WP Fastest Cache, but also AO + Fastest Cache or AO + Async JS) VC works well.

    It seems like I have a conflict, right ? But why did it work well before (I tried with the old versions and have the same issue I haven’t before).

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    powerful mix you have there @marie0638 (maybe too powerful), but the only thing the option in AO does is disabling AO for logged in users. if your page cache shows the cached version (with optimized JS) or if async JS asyncs your VC-code, then things indeed will break. maybe set WPFC not cache for logged in users + configure asyncJS not to async the VC-JS somehow?

    frank

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Box “Don’t optimize for logged in users” doesn’t work’ is closed to new replies.