BuddyPress.org

I had more or less the same problem. Tried the auto-update. Error. Tried overwriting the files. Error. finally deleted the BP plugin, reinstalled, and am now back in business.

@ David Lewis: Buddypress 1.1.3 is the latest “bleeding edge”, isn’t it? And that fix I posted earlier doesn’t work?

I had the same problem, but I followed Davids advice and did this:

All plug-ins are disabled and I have a backup of my db too.

Went to phpmyadmin and in the table wp_sitemeta removed the values by clicking on the edit button from the 3 columns.

wpmu_sitewide_plugins

deactivated_sitewide_plugins

active_sitewide_plugins

Then went to cpanel>mysqldatabases and repaired the database

Then went into my file manager (my site always has issues with cache) and removed any of the long cache folders in wp_content/cache

Went back to my dashboard, left the plugins menu and went back into it and enabled buddypress. Then enabled all the other plugins.

Some the steps I’m sure aren’t needed but it worked for me.

My “sledgehammer” option assumes you have access to your Database… most likely via PHPMyAdmin. Look for a databases option in your web host control panel. Open the database for your site and look for the wp_sitemeta table near the bottom of the list of tables on the left. Open that table. Then click on the “browse” tab to see the contents of that table. Now look for the “active_sitewide_plugins” row (in the meta_key column). Edit that sucker. Just click on the little pencil. And simply delete the junk that is stored in the “meta_key_value”. This worked for me. But please bear in mind… you’re messing directly with the database! And you do so at your own risk. But again… this worked for me. And it should be pretty safe. Just don’t go editing or deleting other things in there willy-nilly. You could bust the entire site pretty easily.

Maybe make a backup before you start. Right when you open the database… click the “export” tab.

Ok. Now I’ve really screwed things up. I thought I could take the advice of Meerblickzimmer and go in to the Plugins folder and rename the buddypress folder (even though it was deactivated already, I thought I could install fresh again and see if that helped.

Now I get this error on an otherwise white screen sitewide:

Fatal error: Class ‘BP_Groups_Group’ not found in /home/litcirc/public_html/wp-content/plugins/bp-group-calendar/bp-group-calendar.php on line 129

Even thought that calendar plugin wasn’t active in the first place. I tried to backtrack by renaming the buddypress folder back to what it was, but the damage is done somehow.

Same error as gsmith above. Very new WPMU / Buddypress install, so BP was the only active plugin. Deactivated it. Upgraded Automatically. Got the error.

Then when in an manually updated, overwriting the still deactivated plugin with 1.1.3. Same error again.

Can someone break down this sledgehammer method in a bit more detail?

Fatal error: Cannot redeclare bp_activity_install() (previously declared in /home/garysmit/public_html/wp-content/plugins/buddypress/bp-activity.php:19) in /home/garysmit/public_html/wp-content/plugins/buddypress/bp-activity.php on line 52

same here…but I took the time to deactivate BP first and all (I don’t have many) plugins too. I deactivated them all. Then I hit upgrade automatically. Got the above error.

Ideas?

the problem seems to be because of multibyte character set(As far as the error is showing).

here is a similar problem reported for forum and Andy suggested to upgrade to php5.

https://trac.buddypress.org/ticket/658

Checkout there

Hope it helps

hi Donnacha

I tried the trunk version on revision 2163.

If you are logged in as site admin,the buddypress will be listed in your plugins,if you are logged in as normal admin,It will not be listed in your plugins.

Hope it helps.

DJPaul offers good advice… A similar issue was raised and confirmed here:

https://trac.buddypress.org/ticket/1265

This issue was resolved (in my case) by upgrading to the version 1.1.3 (just came out). See release history:

https://buddypress.org/about/release-history/#1.1.3

If you still have an issue, try disabling Buddypress and try to reproduce the problem. If the issue is still there without Buddypress, search in the MU forums.

Yeah.. Its possible.. BPDEV use to have a plugin but I think its broken on BP.1.1.2 — I messaged Nicola (the lead evil-genius behind it) and he says that it should be good to go on the release of BP1.2 (currently BP is on BP.1.1.3) — he’ll be working on it on Christmas!

I believe those themes do not work with the latest buddypress.

i’m already a BP consultant, if that can give a hint.. lol

I have no idea what odesk is, but I’m planning to attempt to become a BuddyPress “consultant” in the New Year. Count me in.

I’d like to get a page up for BuddyPress consultants. Perhaps I will start a thread and see if we can get at least a few people posting in there who offer BuddyPress consultancy work. That way there’s at least a list that can be used for the page once it’s up.

This is a great idea, I use oDesk quite a bit and havnt been able to find any Buddypress developers on there so far, I’m not sure how you go about setting up a group.

Yup. Deactivate. Update. Activate. The problem occurs when you don’t do that. I made that mistake myself. I took the “sledgehammer” approach. Went into the DB and deleted the value for “active_sitewide_plugins”. Worked for me.

The problems are all related to this bug:

https://trac.mu.wordpress.org/ticket/1147

ok,here are my thoughts and I will like to go into more details,so would love to hear from everyone of you who has / or is facing this issue.

1.De activate buddypress/buddypress dependent plugin

2.Upgrade buddypress

3.activate it sitewide .

I hope,if you de activated it before upgrading,activation will not generate error,as I have tried on 3 different installs,and I believe the root cause of the error is the sitewide activated plugin upgrade mechanism.

So,It will help everyone ,if the people who go through this ,post their experiences here.May be it can help in investigating further the causes.

There’s always the sledgehammer approach… go into the database in delete the value for the key “active_sitewide_plugins” in the “wp_sitemeta” table.

You are using outdated versions of both WPMU and BuddyPress. I urge you to upgrade.

I also had the same problem last night on a fresh svn check out of https://svn.buddypress.org/branches/1.1/

I just updated to newly released 1.1.3 and now the correct activation link is sent.