Skip to:
Content
Pages
Categories
Search
Top
Bottom

Upgrade to 1.7 broke my site

  • @bezbez

    Participant

    Upgraded to the new version 1.7 and now I am getting the following errors. The whole site is inaccessible. Please help. Using WordPress version 3.5.1
    Warning: require(/home/content/34/1008623/html/subdomain/wp-content/themes/bp-default/_inc/ajax.php) [function.require]: failed to open stream: No such file or directory in /home/content/34/1008623/html/subdomain/wp-content/themes/bp-c_sub/functions.php on line 33

    Fatal error: require() [function.require]: Failed opening required ‘/home/content/34/1008623/html/subdomain/wp-content/themes/bp-default/_inc/ajax.php’ (include_path=’.:/usr/local/php5_3/lib/php’) in /home/content/34/1008623/html/subdomain/wp-content/themes/bp-c_sub/functions.php on line 33

Viewing 6 replies - 1 through 6 (of 6 total)
  • @aitpro

    Participant

    You will need to restore your database from a backup.

    I am not a BuddyPress support person or BP expert, but I am also experiencing the same issues/problems with BuddyPress upgrades. My general theory on this is that during the database update what is happening is that dependent files are not being installed/copied/added in time/i correct sequence for the database update to complete successfully. I could be totally wrong, but that is what it logically looks like at this point.

    Another part of the equation probably has to do with the fact that I have a standard single WordPress installation with BuddyPress and bbPress installed instead of Network/Mulitisite – just a gut instinct/logical guess.

    I am a plugin author and need to get a plugin update out for my plugin in regards to the new jQuery in WP 3.6 which is scheduled to be released in a couple of weeks. Once I get that plugin update out then I will get to the bottom of this and post my findings and a complete tutorial on what to do to successfully install a BuddyPress upgrade given all of particular website’s factors. Will post that back here. Thanks

    @djpaul

    Keymaster

    No, restoring the database for this is like throwing the baby out with the bathwater.

    Your theme looks to be dependant on BP-Default, which WordPress is looking for in wp-content/themes/ (BP-D should never be there).

    I am assuming that because BP-Default isn’t an available theme when BP is deactive (during an upgrade), it falls back to looking inside wp-content/themes/.

    Go to wp-admin > Themes, pick TwentyTwelve. Then upgrade BuddyPress, then re-activate BuddyPress, then switch back to your original theme.

    @aitpro

    Participant

    Ok yeah it is probably just what must be done in my particular case then. I should have stated that better. Something like – if you have tried restoring your previous BuddyPress files and that did not work then try doing a database restore. In my particular case when BuddyPress upgrades do not complete successfully then the only thing that brings that site back up is a database restore.

    @bezbez

    Participant

    @djPaul,
    I can’t even access the admin section of the site. Is there another way to switch the theme? perhaps from the back end?

    @nadiamode

    Participant

    solution 1 – use ftp

    @bezbez rename your current theme folder in root/wp-content/themes/ to theme-bak then wordpress may switch to default theme

    solution 2 – use mysql – go to phpMyAdmin

    – check table “wp_options” edit row “template” and “stylesheet” to default theme example “twentytwelve”

    @aitpro

    Participant

    The solution was so simple. Just use good old fashioned manual FTP upgrading methods.

    Notes:
    1. Deactivating BuddyPress caused a 500 Error and I had to use phpMyAdmin and add the active_plugins db entry back for BuddyPress to bring the site back up.
    2. Doing a WP Dashboard upgrade caused a 500 Error.

    Successful BuddyPress Upgrade steps:
    1. FTP to site and rename the /buddypress folder
    2. Upload the new /buddypress folder.
    For good measure I resaved all BuddyPress settings just to ensure that everything was actually good to go and no problems. Yeah!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Upgrade to 1.7 broke my site’ is closed to new replies.
Skip to toolbar