BuddyPress.org

Until bbPress is a core WordPress plugin, BuddyPress hijacks your forums and takes over the controls.

@katemgilbert

Are you using WordPress MU or normal WordPress?

If you are using MU, follow what DJPaul recomments; create a new MU blog (assuming you’ve selected subdirectory installation); then change the root blog to whatever that blog_id is. That will tell BuddyPress which blog will be the root of all of its features like profiles, directories etc…

If you are using single WordPress, that’s a little different. You could make traditional WordPress page templates for each BuddyPress page that you need, and copy the BP code into your custom WP template. That would allow you to mish-mash the page locations freely.

In addition to what DJPaul said, BuddyPress no longer requires itself to be activated site wide. You can pick and choose which blogs BuddyPress is loaded on in each specific blogs’ plugins screen.

There is a “forums” folder in the BuddyPress plugin. Within that folder should be a bbpress folder. The trunk version does not include the bbpress folder. So if you overwrote your entire BuddyPress folder (or forums folder)… you would no longer have bbpress installed. If that’s the case, just download it and dump the folder in /plugins/buddypress/forums/

BuddyPress 1.2 no longer supports the wire component, so any twitter-to-wire plugins will fail to work in 1.2.

If you want the theme that is on testbp.org, that’s the included bp-default theme with BuddyPress 1.2.

Yeah, go into the WP backend and in the BuddyPress > Components menu, disable Blogs.

Ajax in BP is interwoven with lots of CSS tags. As soon as you change something in templates, Ajax breaks. There are also some known problems with Ajax in version 1.1.3.

Since you’re using the old BuddyPress 1.1.3 themes, you will either need to use the BuddyPress Backwards Compatibility plugin, or update your theme to use bp-classic instead.

I think I know what you’re after and my answer would be – not without customization.

You could have your WP theme as the parent and bp theme as the child. Even with this setup, you’d need to modify the BP theme so it didn’t interfere with the parent which is what you’d want folks to see most of the time.

I encourage you to take a look at the structure of Buddymatic where Ron took Thematic and added the key buddypress templates and functions to create a “unified” parent theme. You could do that or leave the WP stuff as the parent and put your BP stuff as the child. Remember the child “overwrites” the parent so where you don’t want the parent overriden (e.g. home page), you need to remove/rename that file in the child.

I know it’s a bit confusing, but take a look at thematic and the new parent/child structures.

You can also widgetize other areas quite easily and drop BuddyPress widgets in there as you please. You can widgetize a custom page template if you want to. It’s really quite flexible. I wrote a tutorial on how to change different areas of your template files to be able to include widgets: http://wpmu.org/how-to-widgetize-a-page-post-header-or-any-other-template-in-wordpress/ That might help you.

BuddyPress uses regular WP Mail functions. Perhaps they’re getting caught as spam.

https://buddypress.org/forums/topic/when-asking-for-support please

https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/

define ( ‘BP_ROOT_BLOG’, 117 );

Will run on blog ID 117.

BuddyPress can run on a sublog. All you need is this in your wp-config.php:

Will make BuddyPress run on blog ID 2, for example. For other handy commands, see https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/

Like Andy said, when you update the files and visit the admin of your site, then it will upgrade that database.

That plugin may or may not help you out depending on what exactly is broken on your site. In theory that plugin and BuddyPress 1.2-beta should enable your current BuddyPress 1.1-theme and most plugins to work as-is.

Hmm. So like the helloecoliving.com site, you can set up wpmu and load buddypress on a subblog like community? I thought that bp had to reside on the root install. I apologize if I sound like an idiot for not realizing that, but is that the case? This might be the answer to my problem where I can have a standard wordpress site/theme for the root, but a bp enabled theme for the community blog.

Yes, it runs a database upgrade when you update the plugin, it has always done this since 0.1. If you didn’t back up then you’ll need to fix the problems you are having with trunk.

Try installing this plugin:

https://wordpress.org/extend/plugins/buddypress-backwards-compatibility

“Can someone direct me to instructions/tutorials on how to create static pages, “

Go to the admin area of the main blog, find the Pages menu, click Add New.

You only need a BP theme on the blog using BP. (in your case, the Community blog)

With a std install of BP 1.2 you don’t have the ability to activate bbPress plugins, create forums independent of groups, etc. As of this date BP 1.2 only offers limited bbPress functionality from within BP. If you want more functionality you have to copy bb-config.php per the post at the URL below and then access the bbpress at http[yoursite]/wp-content/plugins/buddypress/bp-forums/bbpress

https://buddypress.org/forums/topic/bp-12-and-bbpress-adminplugins#post-34150

If you want to separate non-group forums from group forums so that people don’t see group forums when viewing a list of forums (as seen in a typical standalone install of bbPress) then one way to do that is to do a second install of bbpress. Easiest way is to install BP 1.2, activate the forums in the admin panel, then go copy the /wp-content/plugins/buddypress/bp-forums/bbpress directory to a new location within your site – and be sure to also copy bb-config.php from the bp-forums directory and then edit the file so that it has the correct settings. That’s a simplified explanation, meaning there’s a bit more to it and you need to at least be semi-familiar with installing and administering bbpress software. For example, you probably should have the second copy of bbPress use its own db tables, etc.

I’m in the same boat. Have used a bunch of different captchas including the recaptcha that has been reworked for BuddyPress to no avail. Even took down our registration page for a day to make sure spammers weren’t bypassing via bbpress or somewhere else…. it was nice not having to delete spam accounts for a day. We may end up taking buddypress out at some point here until there are better spam tools in place.