Board Optimization - vBMicroStats

This hack will add at the bottom of each vBulletin (powered) page, the statistics listed below.
Also, it will help you troubleshoot and optimize your vBulletin board by viewing or comparing PHP/MySQL options and other statistics that are normally hidden in your forum pages.

Regular Users:
? Load time of specified page in microseconds
? Number of queries executed
? PHP percent page usage
? MySQL percent page usage

Administrators Only:
? Active users browsing the forum (members and guests) new in 1.1.0
? Server memory usage per page (in Kb)
? Display DEBUG mode status
? Browser GZIP library compression status
? Server average loads
? Uncached templates (useful to troubleshoot the code)

The code modifications were tested into a clean installed vBulletin board. They work 100%.
The hack was tested in vBulletin 3.6.4 and 3.6.5.
If you want to test it into a lower version (3.6.x), let me know.
Also, if you encounter any problems, feel free to post your questions here.

Step by step install instructions are posted into readme.html file.
In order to perform an efficient modification of your files, I recommend you to use Komodo Edit or Textpad.
Both editors will allow you to complete all steps without any coding errors.

The code changes are very safe and designed not to interfere in any way with the vBulletin performance/functionality.
Make sure you modify, save and upload one file at the time to your server.
Then, simply run the product-vbmicrostats.xml file.

[high]The PLUGIN itself is DISABLED by default.[/high]
This was done in order to make sure you properly edit your code first and to avoid surprises.
You will need to enable it, once your code modifications are completed:
Plugins and Products > Manage Products > vB Microstats > Enable (dropdown)
Then, go to your vBulletin Options, click on BB MicroStats setting group and set all your options.

Upgrade to version 1.0.2.
Upgrade to version 1.0.3.
Upgrade to version 1.1.0.

Want to be a guinea pig and try this hack into a higher vBulletin version?
Post your results, so others can read your feedback.

[curriertech]

Originally Posted by kenfuzed

I'm at a loss on how to get this working. I've read through all 14 pages of this thread and didn't find a solution. I installed this on my 3.6.4 board but it won't appear. I've made all the file edits and added the code to my footer, still doesn't appear. I've double checked everything (and yes, I enabled the plug-in). I see the <!-- {microstats} --> in my source code as well.

Is it possible that vbseo or vbadvanced is messing with this?

I run both vbSEO and vBAdvanced, with no issues.

[curriertech]

Originally Posted by StrifeX

It's showing up as 100% and 0% SQL usage. Any ideas?

double-check your file edits.

[kenfuzed]

I can't figure out what I'm doing wrong then. I tried installing this 5 times now and nothing I do even begins to work

[mcyates]

Mine is doing the exact thing.

Page generated in 0.188 seconds (100.00% PHP - 0% MySQL) with 21 queries

Why does it always show 100.00% PHP - 0% MySQL?

Doe I have to edit something on my server to show the % for mysql and php?

Thanks in advance.

[mcyates]

I forgot to do the file edits sorry.

[mtlcore]

Working great on 3.6.7 PL1

What did I do?
I followed instructions: file editing, upload product, enable it from Manage Products page and in vb options.
One more thing: https://vborg.vbsupport.ru/showpost....&postcount=176

How long did it take me?
Less than 2 minutes!

Works great! Thanks a lot dude.

[DaveTomneyUK]

I use Bulletin 3.6.7 and I edited the 2 files but when I try importing the .XML file I get this error.

PHP Code:

The following dependencies were not met: 
1. This product is not compatible with version 3.6.7 of vBulletin. (Compatible starting with 3.6.4 / Incompatible with 3.6.6 and greater) 


[Xplorer4x4]

^If you read the thread or search you will see its been brought up many times before, and you will find the fix.

[DaveTomneyUK]

Originally Posted by Xplorer4x4

^If you read the thread or search you will see its been brought up many times before, and you will find the fix.

OK sorry but I was to lazy to search all 11 pages.

[Adam21]

Still works good in vb368