Franck; weird, did 1.7.3 inline the parent CSS? and is the base URL (http://blabla/) identical to the one your blog is running on?
i recently install bbpress and autoptimize work fine with that.
Thank you
did 1.7.3 inline the parent CSS?
Hum, sorry, I don’t know… I didn’t go into that details as if you remember a crash occurs when selecting css optimization 😉
is the base URL (http://blabla/) identical to the one your blog is running on?
houps, no! Blabla “means” etcetc in “bad” french! 😉
Note that on my real site, I’ll NOT use “inline CSS” as for my point of view, and on my site, I see it more as an overload than as a benefit… Average pages view/visit on my site is around 5. So it’s may be good for the first page (?…) (and for “PageSpeed” (*)…) but I don’t think it’s good for real users. After the first visit, css are cached, and so, don’t need to be reloaded each time (which you do with inlining css).
(*) tools are good, but one need to understand what they measure, and under which context/hypotheses/etc… 😉 … My 0.01%… I’m not an expert… Discussion open here! 😉
@hamed; I still have to create the new POT-file, I’ll mail it to you and the other translators one of the next few days
@franck160; I agree about inlining & tools and such.
regarding the parent CSS; behavior is the same for inlined or normal aggregated CSS, so that means that currently your parent CSS is not aggregated (which is not ideal). most probable reason; your blog is on http://blabla.fr but your parent CSS gets imported from http://www.blabla.fr (or cdn.blabla.fr), in which case Autoptimize considers it external CSS, which cannot be sourced in? This can also be due to PHP not being able to read the parent CSS (because of filesystem rights/ ownership issues maybe).
there’s no problem at all, work excellent as always ❤
Version 1.8 also works fine for me. Great work again!!
Regarding to the ” generate static files” option: If I enable this option I cannot see any changes in my root .htaccess. But if I read one of your posts above, there should be a change, right?
the .htaccess autoptimize generates is in
/wp-content/cache/autoptimize/.htaccess
1.8.0 will be pushed out in a couple of hours. those who have a test-version installed are advised to force the reinstallation of 1.8 once that is out the gates. thanks to all for the feedback on this, I think it is the best version to date!
and I have some nice ideas for 1.9 already. but let’s not rush things, shall we? 😉
i really wonder what feature can be included into 1.9 but i guess and prefer it’s about htaccess cache like what wp super cache do…!
htaccess cache Hamed? Not sure I understand, can you explain?
sure, i mean leverage browser cache with htaccess, preload cache with gzip and you know wp super cache plugin, it’s not just about caching js and css files it’s cache whole website pages. make all website pages static (i know it’s not good for dynamic websites).
ps: i never learn english grammar :))
