vBMicrostats

Finally, the vBMicroStats product for vBulletin 3.5.4 is here.
The previous versions of my mod were very solicited by vBulletin administrators...
I hope you will enjoy this new version as much you did the other ones.

Looking for VB 3.6.x version? It is here.

This mod with 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:
? Server memory usage per page (in Kb)
? DEBUG mode status
? Browser GZIP library compression status
? Server average loads
? Uncached templates (useful to troubleshoot the code)

The code modifications listed below were tested into a clean installed vBulletin board. They work 100%.
If you encounter any problems, feel free to post your questions here.

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

I tried to use the plugin system as much as I could, in order to avoid any unnecessary code modifications.
In order to set the right query execution time, you will need to perform 2 small code changes to each of the following files:
? class_core.php (folder /includes)
? init.php (folder /includes)

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-plugin_vbmicrostats.xml file.

Once the product installed, don't forget to enable it.
Go to your vBulletin Options, click on BB MicroStats setting group and set all your options.

[Boofo]

Yep, a Boofo mistake.

I have the fix for Microstats and Photopost for you, Floren. Want me to PM it to you?

[TECK]

Special thanks to Revan and Boofo for being the guinea pig.
To have vBMicroStats working with PhotoPost, follow those simple steps.

Open pp-inc.php file and find:

PHP Code:

if ( !empty($vbfooter) && $headers != "no" )  
{ 


Replace it with:

PHP Code:

if ( !empty($vbfooter) && $headers != "no" )  
{
    require_once(DIR . '/includes/class_hook.php'); 
    ($hook = vBulletinHook::fetch_hook('global_complete')) ? eval($hook) : false; 


Then install the attached plugin.

[Boofo]

Are you going to add the plug-in to your hack? You could add that in the next version and just make an option to enable it in the settings.

[TECK]

I will not add it Bobby, it's not a vbulletin hack.
I will leave it as optional. It's listed in the first post.

[Boofo]

Well, I added it to mine, but I can see your point.

[TECK]

Ya, not everyone have PhotoPost.
So for those who have it, they can download the plugin and run it.

[James T Brock]

Here are my stats from the first page of the forum.

'Page generated in 0.39097905 seconds (19.32% PHP - 80.68% MySQL) with 11 queries'

I wonder why it's using so much MySQL even though it's just 11 queries???

nevermind... I figured it out. It's because of two of my hacks on the forum index page. One of which is the who has visited today feature.

[TECK]

You mean the init.php file?

[TECK]

The first replacement set is for MySQL, the second one is for MySQLi... you only use one type of connection so that's why it's working.
Notice that the 2 segments are not identical, there is a few bytes difference between them.
In first type of connection you find ($this->sql, $link), then in second you find ($link, $this->sql) in the function.
It's the only difference between the 2 functions.

You probably copied and pasted the same code in both places, thinking they are the same. That results into a parse error.

[TECK]

If you want to display all stats for administrators only, follow the same readme steps.
Install the plugin attached below, instead.