Originally Posted by cscgal

Update:

I just took a look at vB 3.5. Based on what I can see - and this still goes untested - add the .htaccess file as mentioned above. Then, throw all the PHP code into the global_complete hook. The only difference to make is the last line should read:

Help with Code Tags

php Syntax (Toggle Plain Text)

$output = preg_replace($search_array, $replace_array, $output);

$output = preg_replace($search_array, $replace_array, $output);

We're doing a find/replace on the parsed $output instead of the raw $vartext because, quite simply, a hook doesn't exist earlier in the function. So hopefully it will work.


If for whatever reason that above hook doesn't work, the fail-safe way that will 100% work in vB 3.5 is to add the exact code as in the original tutorial below:

Help with Code Tags

php Syntax (Toggle Plain Text)

function print_output($vartext, $sendheader = true)
{
global $pagestarttime, $querytime, $vbulletin;
global $vbphrase, $stylevar;

function print_output($vartext, $sendheader = true) { global $pagestarttime, $querytime, $vbulletin; global $vbphrase, $stylevar;

Originally Posted by cscgal

I am only using up to 3.6.8, and I continue to use $output.

This hack was nevery really supported. It is something I wrote for DaniWeb, implemented on DaniWeb, and then decided to share what was working for me.

As time allows, I periodically stop by and see if I can help anyone out, but that time has gotten scarce over the past year.

Over the course of the past few years, I've added additional rules to the version I personally use, but it is still majorly based off of what I've released here.

After vBulletin 3.7 goes gold, and I am forced into upgrading my own sites to a 3.7 version of this hack, I will most likely offer the 3.7 version that I'll be using in the form of a product xml file.