Skip to:
Content
Pages
Categories
Search
Top
Bottom

Upgraded from 1.0.1 to 1.1.3 and now site is slower with errors in logs


  • Rich Spott
    Participant

    @richs0914

    I just upgraded my wpmu to 2.9.1.1 and also upgraded my buddypress to 1.1.3. Once i did the upgrade (following the instructions) everything said it worked fine, but my site has been running a lot slower and there are tons of errors reading:

    [Wed Feb 10 15:26:42 2010] [error] [client xxx.xxx.xx.xxx] WordPress database error Unknown column 'hide_sitewide' in 'where clause' for query SELECT * FROM wp_bp_activity_user_activity_cached WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 0, 25 made by get_sitewide_activity, referer: http://sportsblognet.com/

    [Wed Feb 10 15:26:42 2010] [error] [client xxx.xxx.xx.xxx] WordPress database error: [Unknown column 'hide_sitewide' in 'where clause']\nSELECT * FROM wp_bp_activity_user_activity_cached WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 0, 25\n, referer: http://sportsblognet.com/

    [Wed Feb 10 15:26:42 2010] [error] [client xxx.xxx.xx.xxx] WordPress database error Unknown column 'hide_sitewide' in 'where clause' for query SELECT COUNT(id) FROM wp_bp_activity_user_activity_cached WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 50 made by get_sitewide_activity, referer: http://sportsblognet.com/

    [Wed Feb 10 15:26:42 2010] [error] [client xxx.xxx.xx.xxx] WordPress database error: [Unknown column 'hide_sitewide' in 'where clause']\nSELECT COUNT(id) FROM wp_bp_activity_user_activity_cached WHERE hide_sitewide = 0 ORDER BY date_recorded DESC LIMIT 50\n, referer: http://sportsblognet.com/

    1. Which version of WP/MU are you running? MU 2.9.1.1

    2. Did you install WP/MU as a directory or subdomain install? subdomain

    4. Did you upgraded from a previous version of WP/MU? If so, from which version? 2.8.6 MU

    5. Was WP/MU functioning properly before installing/upgrading BuddyPress (BP)? e.g. permalinks, creating a new post, commenting. yes

    6. Which version of BP are you running? 1.1.3

    7. Did you upgraded from a previous version of BP? If so, from which version? 1.0.1

    8. Do you have any plugins other than BuddyPress installed and activated? yes

    9. Are you using the standard BuddyPress themes or customized themes? Customized

    10. Have you modified the core files in any way? no

    11. Do you have any custom functions in bp-custom.php? no

    12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in? version 1.0-alpha-6

    13. Please provide a list of any errors in your server’s log files. i did at the top

    14. Which company provides your hosting? Amazon

Viewing 7 replies - 1 through 7 (of 7 total)

  • danbpfr
    Participant

    @chouf1

    You have a missing column in a BP table (wp_bp_activity_user_activity_cached)

    Deactivate BP and reactivate it.


    Rich Spott
    Participant

    @richs0914

    I deactivated and reactivated BP and I am still getting four of those errors every minute. Can I manually create the column? If so do I name it hide_sitewide?


    danbpfr
    Participant

    @chouf1

    Yes you can.

    Here is the code for mysql

    CREATE TABLE IF NOT EXISTS <code>wp_bp_activity_user_activity_cached</code> (
    <code>id</code> bigint(20) NOT NULL auto_increment,
    <code>user_id</code> bigint(20) NOT NULL,
    <code>component_name</code> varchar(75) NOT NULL,
    <code>component_action</code> varchar(75) NOT NULL,
    <code>content</code> longtext NOT NULL,
    <code>primary_link</code> varchar(150) NOT NULL,
    <code>item_id</code> varchar(75) NOT NULL,
    <code>secondary_item_id</code> varchar(75) NOT NULL,
    <code>date_recorded</code> datetime NOT NULL,
    <code>hide_sitewide</code> tinyint(1) default '0',
    PRIMARY KEY (<code>id</code>),
    KEY <code>date_recorded</code> (<code>date_recorded</code>),
    KEY <code>user_id</code> (<code>user_id</code>),
    KEY <code>item_id</code> (<code>item_id</code>),
    KEY <code>component_name</code> (<code>component_name</code>)
    ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1927 ;


    Xevo
    Participant

    @xevo

    Lol, it turned ` into code tags.


    danbpfr
    Participant

    @chouf1

    sorry i used backstiks for inserting de code and now you have to retrive all tags


    danbpfr
    Participant

    @chouf1

    If you like to laught, go here:

    http://jeunessarkozystes.fr

    a BP site full of spam and splog who support the french president.


    Rich Spott
    Participant

    @richs0914

    I just did it manually in phpmyadmin, with:

    hide_sitewide tinyint(1) default ‘0’,

    those settings. It seemed to work fine, no more errors in my logs regarding that. Thank you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Upgraded from 1.0.1 to 1.1.3 and now site is slower with errors in logs’ is closed to new replies.
Skip to toolbar