vbulletin 3.8 problem

[Mark.B]

What version of php are you running?

[testerv]

Anyone know why I am still getting almost one GB of error per day after upgrading to 3.8.7?

[Wayne Luke]

http://www.php.net/manual/en/errorfu...rror-reporting

[testerv]

I upgraded to 3.8.7 and I am still getting about a gigabyte of errors per day in multiple error log files.

How do I turn off deprecated messages in the php.ini file? Is that what Lats is describing in this post, above: https://www.vbulletin.com/forum/show...=1#post2244593

[Wayne Luke]

On 3.8.7? You can turn off the reporting of Deprecated messages in your php.ini file. vBulletin 3.8.7 is not going to be updated to remove them at this point.

[testerv]

I removed all the addons for 2 weeks and I still ended up with 1.2MB worth of these errors daily in my error_log.

[Wayne Luke]

Are your addons up to date?

[testerv]

You need to upgrade to vBulletin 3.8.5 or later.

I am using 3.8.6PL1 and I am getting the error messages by the tens of thousands per week. About 1 gig of errors per day.

[testerv]

I am using vb 3.8.6 PL1 with, according to my Admincp, php version 5.3.5.

Will the upgrade to 3.8.7 PL2 take care of the errors?

[Lats]

If you're getting errors then yes however, in the long run, it would most likely be best to upgrade.

[testerv]

Should this be done in the class_core.php file too?

[Lats]

I had this happen to me on my test install after upgrading a PC and installed a new version of xampp that had php 5.3.

Turns out to be a simple fix, if you didn't want to upgrade, simply find every occurrence of '=&' and remove the ampersand ( & ).

So a line like this in init.php

$vbulletin =& new vB_Registry();

becomes

$vbulletin = new vB_Registry();

[Trevor Hannant]

go into Cpanel or phpadmin and run, a repair database, see if that helps, it cant hurt.

It's nothing to do with that - it's due to his version of PHP and version of vBulletin he's running not fully supporting it. Wayne's advice is correct

[Jazzyname]

go into Cpanel or phpadmin and run, a repair database, see if that helps, it cant hurt.

[Wayne Luke]

You need to upgrade to vBulletin 3.8.5 or later.