Catchable fatal error in wp-db.php on line 429

Yep, I upgraded from 2.7 beta 1 to beta 3 and got exactly the same error ??

I have no idea what is causing it though. It is occurring with the default theme and no plugins activated.

I fixed it by removing line 429. I have no idea if that will have other ramifications though, but it seems to have fixed it in the mean time.

I take that back. It didn’t work at all and caused even more errors to show up.

I did definitely fix it by downgrading to 2.6.3 though. Overwriting the files with the old ones seemed to do the trick.

Fix this by ommitting the addslashes function:

Change the
return addslashes( $string );

into:

return $string;

However much better is to use it like this (for people who don’t have any problem when using magic quotes:

Remove line 429 (return addslashes($string);)

Replace it with this code:

if (!get_magic_quotes_gpc()) {
return addslashes($string);
} else {
return $string;
}

I also have the same problem on one of my sites. trying to narrow the plugin problem down.

if (!get_magic_quotes_gpc()) {
return addslashes($string);
} else {
return $string;
}

didnt work for me but

Change the
return addslashes( $string );

into:

return $string;

did ??

This

Catchable fatal error: Object of class stdClass could not be converted to string in /home/philgons/public_html/wp-includes/wp-db.php on line 429

Relates to the Pages widget which seems broken. Some issue is affecting Pages that have parent Pages. I have raised ticket 8245 for it and other issues.

Thanks for the updates.

Thanks for all the replies.

ryanhellyer, removing line 429 didn’t work, but, pdreissen, both of your suggestions did fix that problem. However, I started getting a different problem, so I rolled back to 2.7b1.

mrmist, good to know the cause of the problem. I removed the pages widget and may trying upgrading again. We’ll see.

mrmist, I removed the pages widget and reinstalled 2.7b3, but I still get the same fatal error. I wonder if there are some other conflicts?

I expect that there are. Even if you do remove the Pages widget, you won’t be able to properly manage pages in the beta 3 until the bug is resolved, because the view page list function is not properly dealing with child/parent pages.

post.php has been fixed now so if you fetch the latest svn you should be rid of this error.

Cool. Just updated, and all seems to be good. Thanks for the tip, mrmist.

I am having this problem now showing up when I try to change my password and I am completely up to date.