An error occurred when saving /home/x/public_html/forum/clientscript/vbsc.js and/or /home/x/public_html/forum/clientscript/vbsc.js.gz. Ensure these files exist and that PHP has permission to write to them (chmod).
=====================================
I have them chmodded to 777 still have a problem.

This has conflict with vMoods

Got the following when running compress CCS

What do I need to do?

Just upgraded to 1.3 nd all is still working perfectly, not sure why others are having so many issues. I've now hosted my images on a CDN too, the site is flying - I just keep clearing my cache so I can see how quick it is! lol. See for yourself:
www.ridehub.co.uk

Quite interested in how you hosted images on a CDN, Is it easy to do??

I get the same at the top of the page, but the Compress shows as being successful.

Everything seems to be working fine.

I really like the idea's of these mods, I just wish that they'd actually improve things instead of possibly cause more issues.

If you're already having page load time issues, some of this addon is going to cause even more problems for you.

You should be loading YUI from a remote source, it means that your users only have to have one set of YUI files cache. If they visit any other VB sites that also load remotely they dont have to request the files. It also increases thier browsing speed of the site because their browser can send requests for these files while waiting for your other site files(by default in browsers only do 2 requests per site at a time). Moving it back onto your site mimimized or not isn't helping. FWIW we already compress the files by default for vBulletin unless you download the package sans compressed javascript. -2

Serving Compressed CSS is actually a good idea, +1

Compressing templates in REALTIME (as in every single page load) is a HORRIBLE idea. This is adding COUNTLESS cpu cycles and making php do even more work then it was already doing to make your pages load. FWIW fully gziped/mod_deflated html with whitepsace removal is 3-5% improvement on average. If you really need to squeeze that much preformance, you should do it ONCE and only ONCE ever. When you save the template you can compress its contents. You can also extend the post cacheing system to compress its html whitespace there as well. -5

The attachment optmizer is probably not bad, but I didn't look at the code here. +0


So overall this addon does more to harm your site than help it, at least as it stands now. Just something to think about :)

Moving Javascript to before </body> +2 (the difference from simply doing that is huge - you don't get those little freezes during page loads)

Google Closure Compiler +1

Compressed HTML I agree that's probably not the best thing for the server CPU :P
I'll make that disabled by default and include a warning in the next version.

Also I could make the YUI files being included in the Javascript cache an optional thing. But still surely almost all the Javascript needed on the majority of pages being compressed into a single file under 70 KB (with GZip) that can be easily cached deserves a +1? :P
Otherwise you end up with a load of separate Javascript files and like you said, it's usually 2 requests at a time (not that it makes much difference without loading them async).

If you want to compress the html, do it, just do it else where like the template save in the admincp, and change how the pst cache works to compress html there.

The YUI files being on a CND (google/yahoo) are better. Its more likely for your browsers to have the YUI files cached if they were hosted on a central website. Why use your own bandwith and cpu cycles to serve the YUI when you don't need to?

YSlow! 2 said that the average vBulletin page gets a C, which isn't bad.

It states that your mod will use NginxHttpGzipStaticModule if available, but is there a windows version of it?

Thanks.