Intrusive front.min.js loads despite W3 Total Cache

  • Hi,

    I use W3 Total Cache, among other things, to combine JSS and CSS into single files (Minify). When I add a script (URL), this script is then loaded in the Minify version in a single file with the other scripts in the cached state of a page.

    For all CSS and JS files entered, the original file is NOT loaded anymore in the cached version of a page. So you can’t see the original path to a certain JS file in the JS section of a browser’s console – that’s the whole point: to minimize many requests.

    Only Cookie Notice behaves differently here: although I specified the exact path (wp-content/plugins/cookie-notice/js/front.min.js), this file is STILL loaded even in the cached version. Although it is now also included in the minify file.

    Why is cookie notice so intrusive here? This file should actually no longer be loaded at all in the cached version.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter dajanas

    (@dajanas)

    PS: By the way, the same intrusive behavior also affects the CSS file wp-content/plugins/cookie-notice/css/front.min.css

    Although entered in W3 Total Cache for CSS minify, it still loads in the cached version of the page.

    No, this is not a problem with W3 Total Cache. The problem occurs exclusively with Cookie Notice.

    Plugin Author dFactory

    (@dfactory)

    Hi,

    That is strange indeed. All those file are added using WP built in enqueue functions, so there should be no exception.

    But we’ll have a look into this.

    Thread Starter dajanas

    (@dajanas)

    I have now uninstalled the cookie plugin, completely removed because of that. I now have a commercial plugin in use, that works fine.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Intrusive front.min.js loads despite W3 Total Cache’ is closed to new replies.