• I had to disable W3 Minify of everything after the latest update yesterday (0.9.5).

    No time to figure out why certain errors appear, but the update broke things for sure.

    • In a CSS file under wp_content/themes/<mytheme>/css/font-awesome.css the fonts are referenced like so: url(../fonts/font-awesome.eot). In the minified CSS I get the the following output and a resulting 404: url(wp_content/themes/font-awesome.css). When changing the font-awesome.css file to read url(fonts/font-awesome.eot) for testing, it works with W3, but it doesn’t work anymore when disabling W3. Somehow the “base url” or something changed.
    • Using GMaps JS InfoBox and have it packed within a JS file. In the same JS file I’m doing new InfoBox(); – throws an undefined error as somehow the packed InfoBox within the same file isn’t loading.

    All errors did not exist before the update. I used all the default minifiers and didn’t change anything after the update. All errors go away when disabling W3 Minify, which is what I did.
    Right now I have switched on Cloudflare Minify and am happy with that.

    • This topic was modified 9 years, 8 months ago by Dennis G.
    • This topic was modified 9 years, 8 months ago by Dennis G.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Does the problem go away when you set the minify to manual mode and set the CSS @import handler to “Process”

    • This reply was modified 9 years, 8 months ago by Scott Hartley.
    Thread Starter Dennis G

    (@m00ntear)

    @import was set to Process already.
    Manual mode would cause all kind of havoc because figuring out the order of all the scripts / CSS is a nightmare as well as adding all these scripts to the list…

    Again: It worked in the previous version prior to 2016-09-25, so the update did break. Judging from the support entries on here many people seem to have problems with the 0.9.5 update.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘0.9.5 Minify (automatic) broken’ is closed to new replies.