Easy Fancybox Conflict with W3 Total Cache

  • Resolved hommealone

    (@hommealone)


    9 years, 9 months ago

    I’m finding that W3 Total Cache is breaking my Fancybox functionality. Curiously, the problem isn’t coming from the js file, but rather the CSS file.

    The problem happens if I let W3TC minify the CSS file.

    I can fix the problem by holding back:
    wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox-1.3.6.pack.css

    from the list of minified CSS files. I can minify everything else and still have proper functionality, but when I minify this CSS file, Fancybox doesn’t work. (Clicking on an image which should appear in Fancybox makes the image appear at the bottom of the page, not in an overlay, and throws a JS error.)

    I don’t know if there is a fix for this, but my work-around (not minifying that CSS file) might help someone else.

    https://wordpress.org/plugins/easy-fancybox/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Rolf Allard van Hagen

    (@ravanh)

    9 years, 9 months ago

    Hi hommealone, thanks for sharing!

    Issues with minification have been reported before (the FancyBox script and CSS are already minified) but I assumed that it came from the script minification not the CSS. But it does make sense because not including the stylesheet gives a similar breaking effect…

    alex80ks

    (@alex80ks)

    9 years, 8 months ago

    I use combination of this plugin with w3 total cache.
    settings that work for me are

    wp-content/plugins/easy-fancybox/jquery.easing.pack.js is embedded in head with non blocking async options.

    wp-content/plugins/easy-fancybox/jquery.metadata.pack.js is before body options and non blocking async

    wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox-1.3.6.pack.css is in all pages and has position last on the list of css files that are minified.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Easy Fancybox Conflict with W3 Total Cache’ is closed to new replies.

Tags