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.

[maxicep]

thanks nice hack,
i got a question how we uncached templates to cached ?

[blockbusted]

Thanks for update.

[Pyrix]

Can I suggest a small change?

Change '{microstats}' to '<!--{microstats}-->' in the template and in the str_replace in the plugin.

This way, on pages where the vb footer is used but it's not designed 'for' vbulletin (for example photopost, mediawiki) it doesn't leave the text {microstats} breaking your table, as it sees it as a comment.

It's what I've done on my site and it works a lot better.

Ollie

[abramelin]

i dont want regular users to see anything, what must i do?

[Snake]

Oh my god! I have been dying to see this hack to be ported over to 3.6.x. Hehe thank you very much, TECK, and welcome back of all sudden!

[TECK]

Originally Posted by Pyrix

Can I suggest a small change?

Change '{microstats}' to '<!--{microstats}-->' in the template and in the str_replace in the plugin.

This way, on pages where the vb footer is used but it's not designed 'for' vbulletin (for example photopost, mediawiki) it doesn't leave the text {microstats} breaking your table, as it sees it as a comment.

Ollie

Excellent suggestion, Ollie. I updated the code.
The file in the first post will still show as 1.0.2 version, since it's just a cosmetic change, it does not replace any of the hack's functionalities.

Originally Posted by abramelin

i dont want regular users to see anything, what must i do?

Hi abramelin,
I'm an old school guy, so I'm not really used to those questions.
The idea with a hack is to open the code and see how is done. I'm sure that if you open the .xml file you will see how to do it rightaway.

Still, is my pleasure to help you. Simply uninstall the product and run the new product-vbmicrostats_admin.xml file instead.
Since I implemented Ollie's request, you will have to edit ONLY the footer template like in the new readme.html file (see first post for the new file, it still shows as 1.0.2).
Leave the PHP files the way they are edited now, they are not needed to be re-modified in order to work with your hack request.

In exchange for my help, promise me this:
You will open the 2 .xml files and look at the code to compare it.

If you still don't understand it, let me know, I will explain you where are the changes.
The idea is to learn what is hapenning inside your code, not just to install a file.
Thanks.

[TECK]

Originally Posted by Xplorer4x4

0KB Used | DEBUG Mode OFF | GZIP ON (level 1) | 0.54 : 0.59 : 0.55 | NO Uncached Template

I have turned debug on in ACP options but it does not show on the forum.

How did you turned ON the debug mode?

Originally Posted by maxicep

thanks nice hack,
i got a question how we uncached templates to cached ?

Show me what you got wrong.

[Xplorer4x4]

Originally Posted by TECK

How did you turned ON the debug mode?

vbulletin options->BB MicroStats->
"Debug Mode"
"Display the Debug Mode status."
Set it to yes.

[TECK]

This is an option to display only the status of Debug Mode, not actually enable it.
I might look into it to automatically enable Debug mode, although, I think is not possible.

I will let you know in few minutes.

[TECK]

Guys and girls, say all Thank You to Xplorer4x4 for this excellent idea.

Version 1.0.3 brings a very powerful option. Now, vBMicroStats can actually turn On/Off the vBulletin Debug Mode.
Make sure you enable this option, ONLY with your board off, orelse it can lead to security breaches (yes, is that powerful).
If your board is turned off to public, you don't have to worry about anything, well sort of.
The best way is to make sure you don't leave this option enabled for a long time either ways.

How to upgrade to Version 1.0.3:
1. Uninstall your current vBMicroStats product. Leave the PHP files the way they are edited now, they are not needed to be re-modified in order to work with the new version.
2. Install the new product, included in the vbmicrostats_103.zip file.
3. Look in the readme file to see how to change the footer template.

You are done. Don't you like those hard upgrades?