Plugin Accelerator

Vbulletin Plugin Accelerator
Accelerate Your Forums Plugins

Summary:

If you use the Vbulletin Plugin System (Specially if you use a lot of plugins), this will help improve the performance of the system overall by inlining all of the plugin code into the PHP files themself.

Essentially making it as if you had hacked the files yourself, this will give you better performance on your forum overall.

PS. Use this in conjunction with my Other Hack (Compress Forum Templates) for speeding up your forum even more by compressing templates.
https://vborg.vbsupport.ru/showthread.php?t=107615
PS. Use this in conjunction with my Other Hack (Template Cache System) for speeding up your forum by caching its templates.
https://vborg.vbsupport.ru/showthread.php?t=110144

Install:

1. Download the zip file.
2. Open install.txt and Read Instructions

Upgrade:

1. Download the zip file.
2. Uninstall Product "Vbulletin Plugin Accelerator"
3. Open install.txt and Read Instructions to install like usual.

Current Status: (RC2)

Release Candidate 2 Has Been Released.
This code has been deemed acceptable and to be used by all.

Please report any bugs back to this thread.
Thanks.

• Latest Changes: 02/11/2006
• Fixed another problem with backslashes, hopefully this will fix some other problems.
• To upgrade, just replace the includes/class_plugin_accelerator.php with the new one.

Important Notes:

1. While this IS a release candidate, more than likely its not fully bug free so Please backup your files before you install this modification, this system is not yet perfect.

2. When running "Rebuild Hook Cache" and "Rebuild All Plugins" if you ever see a small parse error, or file couldnt be opened error; re-run both again and it should go away.

3. includes/hook_files.php contains locations of all the files the accelerator scans for plugin hooks, if you have any files that have been renamed, moved, etc.. you need to add it to that file on its own line, thanks.


If You Have Problems:

If you incur any parse errors, or pages not displaying after running the steps. Please make a copy of the affect file as well as its original version, zip them and upload somewhere. Send me a link to the file for me to download, review and provide a fix.

[Trigunflame]

Originally Posted by Zia

hello...
im not a coder or a xpert...
in easy way...does it help speed up vb3.5.3 ?????
.i read the description mentioned...:S kinda hard to realize..

it will create another plug in system that will work faster than the defult system?




sorry for this kind of raw qus...but im not a coder or an xpert..
thnx

This is alpha quality code, we are just in the testing stages; the current code in the archive simply provides 2 tests that you can run to see if the plugin system code will work on your server/forum/site.

We should have "fully" operational code with the next day or so.

[Zia]

Thans let us try with it in our test site ...

thnx

[uae]

Hey thanks,
But there is no file called static_plugins.php in the zip file!

[Trigunflame]

Originally Posted by uae

Hey thanks,
But there is no file called static_plugins.php in the zip file!

I renamed it to test.php, sorry I'll update page.

[The Realist]

Re: No4 below, what findings do you want?

1) Instructions:
2) Download the zip file.
3) Place the static_plugins folder in your forum directory.
4) Run the script via the url [U]http:// yoursite.com/static_plugins/test.php
5) Report your finding back here if you would please.

[Snake]

/me clicks on the clicky clicky Install button...

[Trigunflame]

Originally Posted by The Realist

Re: No4 below, what findings do you want?

Check the results of test 2 to verify that the ($hook = vbxxxxxx ? : false) is replaced with example php code inside comment blocks.

[Paul M]

So let's just make sure I understand this;

This will scan every vbulletin php file for hook calls, and for each one it will ;-

1. If you have no plugins associated with that hook it will just comment it out

2. If you have a plugin that uses it, it will edit the actual file - to copy the code into it.

What happens when I edit/enable/disable plugins ?

Would it not be less dangerous to copy the plugin code to a php file named after the hook, and just edit the hook call to an include() for that file (have a plugins folder the same as the includes folder) ?

[Trigunflame]

Paul, included I have a file called hook_files.php that list 1 file per line that tell the script which files are permitted to be parsed.

The hooks that have no plugincode associated with it, are commented out in "Accelerated Plugin Style Comment Blocks" for use later (Which Still Saves You an Empty Hook Function Call". If there is a valid hook that there is plugin code, it will insert the code in the correct location inside the files that use that hook.

When you enable/disable plugins, the files that are modified are reverted back to their natural state with their default vbulletin php code.

As for using includes, specifically "naming a file after each hook name", we would encounter 'the law of diminished returns'; as there are 8+ hooks in some files, includes() account for filesystem stat calls while on "Most" pages be faster than an eval() to a large amount of code; still be slower than running it directly from inside the script using it.

Note to Anyone Reading This: None of the above actually Works yet; we are still in testing stages.

[PennylessZ28]

Interesting cocept. I think I'll stick to manually doing my files.