• It works out-of-the-box, and have good quality in most of cases of compression, but, have a compatibility problem with the plugin WP Boxer (by Mark Boomaars), I hope it get compatible with this plugin.

    Edit[19/12/2013]: Problem solved!

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Frank Goossens

    (@futtta)

    Hi danka;
    Some questions first;

    • what does WP boxer do?
    • what type of compatibility problem do you see, what does not work?
    • what happens if you disable javascript (or CSS) optimization in the autoptimize admin page?

    frank

    Plugin Author Frank Goossens

    (@futtta)

    I quickly installed WP Boxer and did some tests. The problem is with the aggregation of 2 CSS-files in WP boxer.

    If I put this:

    /js/nivo-slider/, /js/prettyphoto

    in the “exclude CSS from autoptimize”, it works for me. Can you check if that fixes things for you as well?

    I’ll look into this further in the near future, maybe I can make it so you don’t have to exclude those either.

    Thread Starter danka

    (@danka)

    Thanks a lot for the fast reply!

    It solved the problem.

    Sorry for not being verbose when reporting the bug,
    I was not aware of the details.

    Thanks again!

    Plugin Author Frank Goossens

    (@futtta)

    no problem, but I’ll take that fifth star now if you don’t mind 😉

    Plugin Author Frank Goossens

    (@futtta)

    I’ve been looking into this some more today. The bug does not exist in every theme and it only appears when logged in (in which case admin-bar.min.css and dashicons.min.css are loaded). So instead of excluding js/prettyPhoto and js/nivo-slider, I would suggest to rather exclude

    admin-bar.min.css, dashicons.min.css

    Next to that I’m also adding some extra checks in the CSS optimization-code to fail more gracefully (meaning that although some imports might not be aggregated/ minimized, the CSS won’t be broken).

    The upcoming new version (1.8.0) will have both this “graceful failure” and the exclusion of both admin-css-files.

    Thread Starter danka

    (@danka)

    no problem, but I’ll take that fifth star now if you don’t mind 😉

    Yes, you can take, you deserve it… I was not expecting that fast response…

    Thanks again…

    If you dont mind, I would like you to take a look at this suggestion http://wordpress.org/support/topic/feature-suggestion-22

    Until now, I dont know any good and functional plugin that does what I suggest there… if you could look and try to implement this, I would be grateful… 🙂

    Plugin Author Frank Goossens

    (@futtta)

    I’ll take your suggestion under consideration.

    But regarding the fifth star; I can’t take that, you’ll have to give it to me 🙂

    Thread Starter danka

    (@danka)

    Hello,

    I was just fiddling with my site codes, testing it in Google Chrome, and everything was working all fine together autoptimize, when I thought to test it in Firefox (latest), then, I found that my site was broken, all jquery JS codes does not work, then I gone to autoptimize and disabled it, and tested again in Firefox, and then it worked fine again.

    Why browsers need to be so different from one to other?!? I was very happy that my “minified” site was all good. 🙁

    Plugin Author Frank Goossens

    (@futtta)

    I feel your pain 😉

    Although it can work when aggregating jQuery & it’s plugins, I find that it is error-prone to do so. Hence the best way forward would be to exclude jQuery (jquery.js or jquery-min.js) but maybe some jQuery plugins from being autoptimized.

    Plugin Author Frank Goossens

    (@futtta)

    Before excluding jquery outright, you could first also try to first “force js in head” and then combine that with “look for js only in head”.

    Thread Starter danka

    (@danka)

    What is more curious to me is that a language like JS should be portable across all browsers, dont matter what you do, but, working daily on it, from day to day, it start to resemble more compiled languages like C++… I am loosing much time trying to compatibilize codes across browsers than creating new code! It was not suppose to happen!

    Jquery was already excluded and it still does not work on Firefox! I will try your suggestion and force all to head….

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Very good’ is closed to new replies.