Log in

View Full Version : vBulletin Upgrade Problem


taffy056
01-09-2005, 01:06 PM
Hi,

After upgrading from VB 3.0.3 to 3.0.5 I get the following errors when I try to read certain threads, this only happens where members have posted messages, where guests post messages there is no error. So this leads me to beleive that it is the warning hack that causing this problem, has anyone had this problem upgrading, and can someone suggest a solution.

Warning: Invalid argument supplied for foreach() in /includes/functions_showthread.php on line 695


Forum Message

Unable to add cookies, header already sent.
File: /homepages/26/d90465391/htdocs/wsc92543615/forum/includes/init.php
Line: 27

Thanks,

taffy

Dean C
01-09-2005, 01:25 PM
If the warning hack is the only modification you have installed I would suggest making sure you have re-applied the changes correctly and if you have ask for support in the warning hack support thread :)

taffy056
01-09-2005, 01:38 PM
Hi Dean,

I have posted a question there about deleting and then re-installing the hack, I have other hacks installed (below) as well, but they appear to be up and running correctly, the only one I seem to have a problem with is the warning hack. But I was only asking here in case someone else could help, also it in case it wasn't the warning hack at all.

PetzVB v2
v3 Arcade
RPG
vBookie
vbChat
vStocks
Shoutbox Hack 1.04b

Deaths
01-09-2005, 01:42 PM
With me uShop caused the error, but I think for you it's v3 Arcade ;).

You need to re-apply the changed made to init.php.

taffy056
01-09-2005, 02:44 PM
Hi,

I have just removed line 27 (below) in the init.php file, and everything is working correctly, what does this piece of code do, and with it removed will it have adverse effect on anything?

echo "<br /><strong>Warning</strong>: $errstr in <strong>$errfile</strong> on line <strong>$errline</strong><br />";

taffy

Dean C
01-09-2005, 02:54 PM
Won't do any harm removing it :) It looks like a debug facility that forgot to be removed.

taffy056
01-09-2005, 05:02 PM
Thanks Dean :)

Won't do any harm removing it :) It looks like a debug facility that forgot to be removed.