Status
Not open for further replies.

Chase

New member
My server just upgraded their PHP to 5.3.19.... and I am getting this weird error when navigating your product in my admin panel

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 55

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 107

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 111

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 119

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 130

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 134

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 142

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 211

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/init.php on line 389

Deprecated: Assigning the return value of new by reference is deprecated in /home/eagl1/public_html/myaccount/includes/class_core.php on line 2552
 
It looks like I also get this error message when I try to manage my credits... its at the top of the screen.
 
I'm surprised they haven't fixed this yet...

To fix, use Notepad++'s find and replace all in folder function, change

Code:
error_reporting(E_ALL & ~E_NOTICE);

to

Code:
error_reporting(E_ALL & ~E_NOTICE & ~8192);

These errors come from vBulletin.
 
Or you can open the mentioned files and changing =& new to = new

The reason why they are refusing to fix this for vBulletin 3.x is because they need to support legacy versions of PHP - we recommend either staying with PHP 5.2 or upgrading to vBulletin 4 for this reason. vBulletin 3 is no longer being updated to fix these kinds of errors.

You will also see the same errors when posting a new post, or anywhere else BBCode is mentioned.
 
Status
Not open for further replies.

Legacy vBCredits II Deluxe

vBulletin 3.8.x vBulletin 4.x.x
Seller
DragonByte Technologies
Release date
Last update
Total downloads
845
Customer rating
0.00 star(s) 0 ratings
Back
Top