Search results for query: *

Ah this makes sense, the plugin is using the same hook locations as the normal vBulletin WOL, however the database object isn't the same variable/globalised within the CMS. I can resolve this tonight for you, I'll update this thread once the fix is live :)

Hmm, could be some collision. I'll try get my hands on the latest version of vBET and see what can be done :)

I'm not sure what the issue is here unfortunately, the chart is indeed loading and feeding the correct data. If you have Firefox + Firebug installed, is the console reporting any errors?

You mean you can't disable the feature in vBET, or you only want it disabled where vBET is involved? Edit Saw your updated post. If vBET caching is only partial for guests, I would disable their guest caching and keep vBO's enabled, it wouldn't make much sense to have 2 systems handle the same...

If that's the case, you can either disable vB Optimise Guest caching or vBET if the same thing is being accomplished :)

Hey Blinkster, I logged on using the details you provided and the chart loaded fine for me. The screenshot is below. Perhaps you could try different browser? Although it worked in IE/Firefox/Chrome for me.

Are you using a specific Widget for showing users online within the CMS? Unless I'm mistaken it's not default functionality.

Well actually there is a lot of use in keeping it cached in Guest Caching. When vB Optimise caches a page, it doesn't store specific data for components - it stores the entire page output which includes whatever the page is displaying, then when returning this it avoids all the SQL queries...

Hmm, I'd re-download the license again and upload /vboptimise/swf/ folder in ASCII mode via FTP. If that fails I'd only be able to help with a temp admin login (doesn't need to have any perms since vBO is global in ACP) if that's possible.

Hi Taurus, Can you tell me if you're running vB3 or vB4, and if by homepage you mean the forum index/CMS or some other default entry page. Thanks :) Disabling the WOL Cache should prevent the error for now until I can find out what's causing it.

Yeah you'll need to go to the blocks manager, forgot about that one: ACP > Forums & Moderators > Forums Block Manager > Edit Each block has a cache time (typically 60 minutes), you can reduce this. After changing you can flush the vB Optimise cache so it's upto date :) In regards to the chart...

1) The results are displayed via flash, does the chart load for you okay? 2) vB CMS does have its own TTL on data, you can go to ACP -> vB CMS -> Widgets -> Click "configure" on the blocks taking a while, and adjust the value for cache time (or refresh time). Once adjusted you can click "clear...

Yep, the MySQL table is used to record the stats :) Let me know if you have any further questions/issues.

Has happened with certain installations when upgrading from Lite/Pro. Uninstall the product XML and re-install, you'll lose your settings (albeit, not much) but it should create the MySQL table for you :)

Gotcha, what about the arcade issue you mentioned?

I'm not sure what you're referring to? vB Optimise isn't designed to fix flaws/bugs, just optimise segments of vBulletin by storing data in cache and fetching it from there opposed to the database, with exception to Guest/Aggressive caching will also eliminates approx 90-97% php runtime processing.

You can find the full details here: http://www.dragonbyte-tech.com/vbecommerce.php?do=purchase&act=product&id=1 Along with more data to cache to save querieso and vB CMS optimisations v2.3 Pro provides guest caching which for guest-heavy forums reduces massive load from your server. In the...

Recommended: Turn all cache options on :) I'd suggest running a system test too so you can verify everything is working properly.

The cached content for guests if configurable, so you can have it cached for 1 minute or X hours if you choose. Keep in mind that there is a global TTL (time to live) on all cache too which overrides everything, so if you set guest cache to 2 hours and global ttl to 1 hour - then it would only...

That error means the files have not been uploaded in the correct locations, or partial hooks are missing (which they shouldn't). Please verify the files are located in /home/SITE_NAME/public_html/vboptimise/