BuddyPress.org

Andrea is correct. The grab a shovel phrase is only meant as an analogy to say that the best way to get what you want done is to do it. If you can’t, that’s okay too, and try not to be upset if someone else isn’t doing it either. There’s no rush to push the […]

Huh… Very bizarre.

I consider deleting and reinstalling as admitting defeat, which isn’t something I take lightly. 🙂 But if your site is in a position to be able to start over, it’s a good way to rule pretty much everything else out.

No harm done and I think we all feel better after a little conversation.

On top of everyone’s ideas, be sure to check out how to correctly attach your plugin to bp_init: https://codex.buddypress.org/how-to-guides/make-your-plugin-buddypress-aware-v1-2/ Because of the way that WordPress loads plugins, its possible that bp_init is firing before your plugin has added the hook. If that’s the case, your function is safe to…[Read more]

Yes but it modifies the xprofile database table so you will want to take care when using it. I believe it’s simply titled “XProfile Privacy”

Anything that says something close to:
define( 'NONCE_SALT', 'unique phrase goes here' );

There will be a few places it will appear all one after the other. Your best bet would be to visit the Salt Generator and use those, as they are totally randomized and guaranteed to be unique.

I’ll need to look at this specifically for you this weekend.

@andrea_r is right. There is a manual edit you’ll need to make to your .htaccess file after upgrading to 3.0. Wp-content/blogs.php to wp-includes/ms-sites.php I believe? Not at my computer at the moment to say for sure.

Are you using a language other than English, and have you adjusted all of the default WordPress security keys and salts in your wp-config.php file?

This is a known issue that is becoming more widespread but does not have an immediate solution yet.

Hey all! There were some issues with strings in 1.2 that have been slightly adjusted in every following releases. Even though we’ve had a string freeze, these were mostly functional issues with %d instead of %s, etc… If you can post a trac ticket in milestone 1.2.5 with these same references, I’ll be sure to […]

Can someone post this as a bug in the trac for 1.2.5 milestone please? I’ll be sure to get it fixed in the next release.

Odd. Can you confirm the settings in your bb-config.php match your DB settings, etc…

Can you reply to existing topics? Or just cannot create new ones? Does this happen for all groups?

Haha 🙂

Good points both of you. I for one will make a better effort to peek around the forums more in the coming days. There are plans and ideas to “fix” BuddyPress.org to bring back the functionality you’re used to, so bear with it for now and know that things will improve. 🙂

For those of you that want to directly influence the future of BuddyPress, http://trac.buddypress.org. Make it your friend. Learn it. Love it. Live it. Give it a hug everyday and patch a bug. The Trac is where you can post code snippets, or giant mega patches of code that you think should be integrated into […]

No need to worry. All is well. 🙂 I can assure you BuddyPress is 100% not abandoned. My excuses are more client work than I can handle, and building lots of core API’s to make extending BuddyPress /much/ easier in 1.3. Custom post types in WordPress 3.0 have me sidetracked also 🙂 I’ll post something […]

WPMS. Was an upgrade from a previous version via the WP updater.

This is fixed in the 1.2 branch of code and will be fixed in 1.2.5.

As an update, I’m working on fixing this for all installs this week.