SBlueman - Enable vBulletin debug info to see if vB Optimise is working properly :)

Update: I've patched the release to 1.2.1 to fix the issue SBlueman discovered :)

I confirm.

1. Installed product. Not "enabled" in settings. Only defaults used.
2. Gone to settings, selected option "Keep CSS in file" and pressed "save"
3. Got the same error.

Then switched product off, did all settings, and enebled product again :)

Vitaly, the patch I gave SBlueman works, or you can update to 1.2.1 :)

Sorry, I'm not ready to such extreme experiment, as disabling vbseo even for 1 minute at production site :) .

If you will not succeed to find problem in nearest days, PM me, i'll give you admin account at my "development" forum copy. It's busy now for another tasks.

Heh, your support is as fast and professional as at vbseo forums :)

Will do measurements in nearest days.

Btw, try to ask "happy installed people", how much of them use apache+mod_php instead of nginx/lighttpd+php_fcgi :) .

Off top of my head, probably a lot more, like 90% upwards. Ofcourse, if a vB mod could change that, I'd of already included it :p

As for disabling vBSEO, no worries, I understand how it is sometimes :)

I am running 3.6.8 and vbSEO and it seems to be working for me....although I don't know how to gauge that even after enabling the debug info.....bit of a noob when it comes to that.

SBlueman - After enabling debug mode, refresh your forum, and look at the very bottom for a drop down menu, click it and you'll see messages in there from vBulletin and vB Optimise, you should be seeing messages that say vB Optimise has fetched x, y and z from cache :)

LOL. You have to introduce payed "pro" version with installation service :) . vboptimiser + nginx proxy at frontend...