Upgrade to 3.8.4, but still deprecated messages

[Karel Souffriau]

Hi,

I've just upgraded vBulletin to 3.8.4, but I'am still getting deprecated messages:



And the same errors in private.php (when opening privé messages).

[Andy Huang]

That's odd. Please post the exact error for private.php, and any other place you're noticing this, so I can check them out...

[Andy Huang]

I am unable to reproduce this on my php 5.3.0 development environments (Windows XP + Apache + PHP 5.3.0 and Linux + Apache + PHP 5.3.0).

Please check your php settings to make sure that error_reporting is not marked as a disabled function or alike, as we need to use that to override the notice messages. Additionally, please provide the exact procedures that you were following which caused the message to trigger, so we can do further tests on our test bed.

Thanks.

[Karel Souffriau]

That's odd. Please post the exact error for private.php, and any other place you're noticing this, so I can check them out...

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/.../private.php on line 147

And on line 1524, 1527, 1639, 1642, 1738, 1741 and 2100.

[Karel Souffriau]

I am unable to reproduce this on my php 5.3.0 development environments (Windows XP + Apache + PHP 5.3.0 and Linux + Apache + PHP 5.3.0).

Please check your php settings to make sure that error_reporting is not marked as a disabled function or alike, as we need to use that to override the notice messages. Additionally, please provide the exact procedures that you were following which caused the message to trigger, so we can do further tests on our test bed.

Thanks.

Gonna check my php.ini

The strange thing is, I'm getting this messages only when opening the page for the first time. After that, I can refresh the page 1000x without getting any deprecated messages.

[Andy Huang]

I'm guessing there's some cache thing setup on your server which was still caching the 3.8.3 code or something. Please do let me know if you find any way to reproduce this problem though.

[Karel Souffriau]

Hmm, that's possible. We're using xdebug, maybe this is the cause of our problem.

I keep you updated.

[SecondV]

Same thing was happening to me, however I cleared APC (cache) and everything's fine! :)

[SecondV]

take that back, still happening in some places for eg:



[14-Aug-2009 19:50:12] PHP Deprecated: Assigning the return value of new by reference is deprecated in /home/*/member.php on line 353
[14-Aug-2009 19:51:33] PHP Deprecated: Assigning the return value of new by reference is deprecated in /home/*usercp.php on line 126
[14-Aug-2009 19:51:36] PHP Deprecated: Assigning the return value of new by reference is deprecated in /home/*/profile.php on line 733
[14-Aug-2009 19:51:47] PHP Deprecated: Assigning the return value of new by reference is deprecated in /home/*/private.php on line 147

eg, line 147 in private.php is:

$bbcode_parser =& new vB_BbCodeParser($vbulletin, fetch_tag_list());
=& new - is the problem.

[Andy Huang]

=& new is not the problem... well it is and it isn't.
It is what will trigger the deprecated message, but the message is not suppose to come up because it should be disabled by the error handling procedures.

If you are not seeing the messages on screen, but are seeing them in the error logs, then it is caused by a bug in PHP 5.3.0: http://bugs.php.net/bug.php?id=48843 which we can't do anything about.

If you are seeing them on screen, then it may be something else, such as a caching problem.

[dieselpowered]

I was receiving the following error:

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 55

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 107

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 111

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 119

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 130

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 134

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 142

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 211

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/init.php on line 389

Deprecated: Assigning the return value of new by reference is deprecated in /xxxx/xxxx/xxxx/forum/includes/class_core.php on line 2552I ended up removing the '&" where it was '=&' and the problem went away. 3.8.4, PHP 5.3.0.

[Dilly]

I was receiving the following error:

I am receiving this error when clicking on Manage Tabs in AdminCP...any thoughts?
I ended up removing the '&" where it was '=&' and the problem went away. 3.8.4, PHP 5.3.0.
Re-read the last post. It's a poor man's fix.

[dieselpowered]

Thanks for the response Dilly, I did actually read that and still receive those errors...error reporting is on in the PHP.ini so I am not sure what is going on. The only successful way to get those errors to go away was to remove the "&"

Any other ideas?

[PitchouneN64ngc]

Wait for PHP 5.3.1? Or update to PHP 5.3.1RC1? :)

[dieselpowered]

True, maybe just leave the file edits in place until a new PHP version is released.

[digitalpoint]

I was also seeing the issue, but for whatever bizarre reason it seemed to only be happening the first time the file was accessed after Apache was restarted (maybe something weird with that file when it's not being hit on the caching system or something?)

I didn't (don't) care all that much though since it only happens once (after httpd2 restart) and only for admin (me), so not like anyone else sees it.

[PitchouneN64ngc]

Ok i checked a little, and it seems with 3.8.4, i have again these messages but in error_log file. If error messages appears in forum, it should be because your PHP configuration have "display_errors = On;".

But these errors make my error_file 91MB! There isn't any other fix we could have for 3.8.5?