Skip to:
Content
Pages
Categories
Search
Top
Bottom

Disabled BP, re-enabled BP, now wp-admin shows slew of MySQL errors!

  • @vtowel

    Member

    Hi there,

    We have a multi-site WordPress 3.0.1 installation with BP 1.2.5.2 installed.

    Today I just accidentally clicked “Network Deactivate” for the BuddyPress plugin, when I meant to deactivate a different one. Realizing my mistake, I immediately clicked “Network Activate” again for BuddyPress, and wp-admin came back with a page filled with a slew of these errors:

    Warning: mysql_real_escape_string(): 8 is not a valid MySQL-Link resource in /home/wmaster/yexpress.net/wp-includes/wp-db.php on line 785
    Warning: mysql_real_escape_string(): 8 is not a valid MySQL-Link resource in /home/wmaster/yexpress.net/wp-includes/wp-db.php on line 785
    Warning: mysql_real_escape_string(): 8 is not a valid MySQL-Link resource in /home/wmaster/yexpress.net/wp-includes/wp-db.php on line 785

    BuddyPress looks to be active again, because I can see the admin bar up top, and our home page is looking okay. But WP Admin side was basically unusable because it was just crammed with the above errors.

    So in my panic so as not to halt our team’s development I changed the offending function so that PHP warnings would be suppressed:

    ` function _real_escape( $string ) {
    if ( $this->dbh && $this->real_escape ) {
    $orig_level = error_reporting();
    error_reporting(E_ALL ^ E_WARNING);
    $result = mysql_real_escape_string( $string, $this->dbh );
    error_reporting($orig_level);
    return $result;
    }
    else
    return addslashes( $string );
    }`

    At least now wp-admin is somewhat usable, though there are still a handful of similar MySQL errors still appearing in the header of every wp-admin page request:

    Warning: mysql_error(): 8 is not a valid MySQL-Link resource in /home/wmaster/yexpress.net/wp-includes/wp-db.php on line 922

    Another serious problem I noticed is that the “admin” account I’ve been using, which is supposed to be a WPMU Super-Admin, has lost a lot of its rights. For instance, I can’t administer the global users table, or modify the available plugins to activate for sub-sites…

    Any help would be so appreciated! I’m a bit panicky because my other developers need to be able to use wp-admin regularly.

    Thanks…

Viewing 5 replies - 1 through 5 (of 5 total)
  • @vtowel

    Member

    Also noticed this error on the Dashboard under the QuickPress section:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 64 bytes) in /home/wmaster/yexpress.net/wp-includes/wp-db.php on line 1315

    @tekuan-coleman

    Member

    i see your second error on my pahge couldnt get any plugins or i would get the same message when i tried to download a pluggin.. i called my host and they add extra memory space so im not sure if it’s a wordpress/bp problem or not

    *

    @vtowel

    Member

    There’s no reason we should suddenly be exceeding 256 MB of memory on every wp-admin dashboard request. I think this must be related to the MySQL-Link errors.

    @djpaul

    Keymaster

    BuddyPress shouldn’t cause these problems. I would suggest you check/repair the database tables, as that seems a more likely cause of these problems. I imagine that if you disable BuddyPress, you’ll still have these problems. If, however, disabling BuddyPress fixes everything, delete all of your BuddyPress files and re-upload.

    @vtowel

    Member

    Thanks for the quick reply, Paul. I did what you said, and the errors disappeared so long as BP was disabled. They came back as soon as I re-enabled it. But at least now I have super-admin access again. I had to disable all the plugins to get that to happen.

    I did a mysqlcheck on the database – nothing needing repair.

    Maybe one of the other developers modified BP core? Well, no worries for now. We have another instance of the site that we might try to mirror.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Disabled BP, re-enabled BP, now wp-admin shows slew of MySQL errors!’ is closed to new replies.
Skip to toolbar