• When Autoptimize is active, Facets from FacetWP are not displayed on pages. When Autoptimize is deactivated the facets do appear and function properly.

    I have tracked down the conflict to existing between Autoptimize & FacetWP by deactivating all other plugins (though interestingly enough I did discover another instance of a conflict that occurs between Lazy Load By WP Rocket & FacetWP in which the facets appear on the page but do not function).

    I have attempted to exclude individual FacetWP plugin files as well as the entire FacetWP plugin directory of ‘wp-content/plugins/myFacetWP3.4.5/’

    Does anyone have experience with successfully running FacetWP & Autoptimize together?

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

    (@optimizingmatters)

    First and foremost try to identify what is breaking your site by just disabling CSS or JS or HTML or Image optimization (incl. lazyload). Once you know that we can decide on next steps.

    There’s more info in the troubleshooting tips and info on exclusions in the AO FAQ.

    hope this helps,
    frank

    Thread Starter MindCreatesMeaning

    (@xizor)

    Optimizing HTML is the culprit for making the facets disappear. This raises an interesting question, because how can one minify HTML and exclude one plugin from being minimized?

    Optimizing JS is the culprit for making the facets work or not work. Excluding the plugin folder ‘ wp-content/plugins/myFacetWP3.4.5/ ‘ causes the facets to disappear. I can’t seem to make them appear and work at the same time.

    Optimizing CSS doesn’t appear to have any effect.

    The only way I can get the plugin to work with Autoptimize is to Not optimize HTML or JS. (Not something I want to do because it defeats 2/3rds of the purpose of Autoptimize which I enjoy using).

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    re. HTML minification; that’s the least important one, but just to be sure; you’re coincidentally not using W3 Total Cache, are you? Because there’s a known problem when optimizing HTML with AO when W3TC is installed ..

    re. JS; what JS errors do you see on the browser console when myFacetWP3.4.5 is or is not excluded from JS optimization?

    Thread Starter MindCreatesMeaning

    (@xizor)

    With myFacet2p3.4.5 NOT EXCLUDED there are zero JS console errors upon initial page load. The following error appears only upon user interaction with a facet:

    Uncaught SyntaxError: Unexpected token u in JSON at position 7991
        at Function.parse [as parseJSON] (<anonymous>)
        at Object.success (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569)
        at c (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:186)
        at Object.fireWith [as resolveWith] (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:188)
        at l (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:434)
        at XMLHttpRequest.<anonymous> (autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:440)
    success @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
    c @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:186
    fireWith @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:188
    l @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:434
    (anonymous) @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:440
    load (async)
    send @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:440
    ajax @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:411
    FWP.fetch_data @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
    FWP.refresh @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
    FWP.autoload @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
    (anonymous) @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:569
    dispatch @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:255
    v.handle @ autoptimize_e0e728fd5859c0380238cbfc1729a1b0.js:248

    When myFacetWP3.4.5 IS EXCLUDED there are 3 JS console errors upon initial page load. (No interaction is possible because facets do not appear on screen.)

    The 3 errors are:

    Uncaught ReferenceError: jQuery is not defined
        at autoptimize_single_f6cf72b14b8588f3810eb056b7253107.js:1
    
    Uncaught ReferenceError: jQuery is not defined
        at front.min.js:1
        at front.min.js:1
    
    Uncaught ReferenceError: jQuery is not defined
        at autoptimize_single_5b97a9665877ae41e3f1e28eecb19285.js:42
    Plugin Author Optimizing Matters

    (@optimizingmatters)

    OK, keep it excluded, but make sure jquery (js/jquery/jquery.js by default) is also excluded and not asynced or deferred somehow?

    Thread Starter MindCreatesMeaning

    (@xizor)

    Hmm, I’ve done this and it has not worked. I’m at a loss for now.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, what JS errors do you see with that configuration?

    I have similar issue too with facetwp.
    If any options enabled css or js its showing at console:

    Uncaught SyntaxError: Unexpected token   in JSON at position 122523
        at JSON.parse (<anonymous>)
        at Function.n.parseJSON (jquery.js?ver=1.12.4-wp:4)
        at Function.a.parseJSON (jquery-migrate.min.js?ver=1.4.1:2)
        at Object.success (front.min.js?ver=3.5.8:1)
        at i (jquery.js?ver=1.12.4-wp:2)
        at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
        at x (jquery.js?ver=1.12.4-wp:4)
        at XMLHttpRequest.c (jquery.js?ver=1.12.4-wp:4)

    JS excluded: wp-includes/js/dist/,wp-includes/js/tinymce/,jquery.js, /facetwp/, jquery-migrate.min.js,

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    As per the forum guidelines can you create a new topic for your problems + add a link where I can see this happening ?

    thank you,
    frank

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘FacetWP 3.4.5 & Autoptimize 2.6.1 Conflict’ is closed to new replies.