BuddyPress.org

Here’s how to get around activation. I was having the same problem on my test server, since it couldn’t send out activation emails. If you need activation emails enabled, then this workaround will not work for you.

For users that have already been created and cannot login, you can go into the wp_users table in the database and change their ‘user_status’ from ‘2’ to ‘0’ (if you have database access). ‘user_status’ is not used in WordPress — it’s a dead field — but Buddypress uses it to redirect to the homepage if a user has not been activated (aka user_status=2).

To avoid the problem for future user registrations, you can change a file to avoid activation (if you have FTP access). In the buddypress plugin directory, find bp-core/bp-core-signup.php. Find the line that says:
`$wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 2 WHERE ID = %d”, $user_id ) );`
In my installation (1.2. it is on line 357. Change the 2 on that line to a 0. So it should look like this:
`$wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 0 WHERE ID = %d”, $user_id ) );`

Now when a new user is created, they will automatically be able to login without their email needing to be confirmed.

We can’t see what that file parses and outputs! It looks as though there is no structure?

So do a number of those function calls describe markup structure? You will need to look at them and edit or copy where necessary; however you shouldn’t really be having an issue? you view the generated output of an index.php or page.php and match that to a buddypress page and ensure that the BP page matches to your themes. What structure does the file above generate? it should match to the other pages in your theme and is the structure that your BP pages need to duplicate.

@famous, you are right about that. searching multiple blogs is too costly on database if the posts are not cached in a global table. The unified search does not includes it because most of the sites do not use any sort of global post caching, and searching the posts on a network of say more than 20 blogs will be too much for a shared server to handle. I remember there is a plugin https://wordpress.org/extend/plugins/multisite-global-search/ which does global search.
The problem is, It will put some real strain on database. if you still want to use it, you can extend the unified search with the above mentioned plugin.

hope that helps.

However, that’s running BuddyPress 1.3.

BuddyPress 1.2.8, which is the current version, does have a couple of small issues that we’ve noticed so far with WordPress 3.2, mainly with javascript in the BP-Default theme. If anyone spots any more, please let us know. We plan a same-day release of 1.2.something with WordPress 3.2 to address these.

You can get the latest in the 1.2 series from https://buddypress.trac.wordpress.org/changeset/4550/branches/1.2?old_path=%2F&format=zip (at time of writing. SVN is https://svn.buddypress.org/branches/1.2/)

You can do all that when you transform your single WP into a multisite installation by creating a network with subdomain structure https://codex.wordpress.org/Create_A_Network
Multisite support forum – https://wordpress.org/support/forum/multisite

“same content” – if you mean that each user has a portfolio page, or about me page, a contact us page, etc. this can be achieved by creating a custom theme which you can designate as the default theme for each new subsite created by your members.

Create a network/go multisite before installing BuddyPress plugin if you want to add social networking features – https://codex.buddypress.org/getting-started/before-installing/

wp in multisite/multi-user mode is for multiple blogs on the same installation, if that’s what you mean…

https://codex.wordpress.org/Create_A_Network

EDIT: darn it – beaten to it by moments….

You might start out small. Install BuddyPress and enable just the activity stream; disable everything else. Make sure that the theme css works well with the activity stream. You’ll need to install the BuddyPress template pack. After you are satisfied with the activity stream then change WP install to multi-site. You’ll want to lock it down so that you control creation of blogs – so that you don’t have to deal with splogs. Once you have that working then you can add a few other BP features – private messaging, etc.

You can see 3.2RC1 on the BP Test site:

http://testbp.org/

I can’t see how it could be a caching issue. Are you on multisite or regular WordPress, and do you mind sharing what’s in your .htaccess file?

@triznic have you tried to work on what I posted above?

get_sidebar appears in footer.php for the intrepidity theme https://themes.svn.wordpress.org/intrepidity/1.5.1/footer.php so following the structure of your theme onto the activity/index.php file, you don’t add any get_sidebar calls in the other BP template files

WP started out primarily as a blogging tool.

The default home page for BuddyPress using the bp-default theme is the blog index page like you see at http://testbp.org/

If you want a static page in front page and have a “blog” link read https://codex.wordpress.org/Creating_a_Static_Front_Page

It’s possible that the server isn’t sending any mail….

Some web hosting services need an extra plugin to send mail. I have successfully used: https://wordpress.org/extend/plugins/wp-mail-smtp/ but there are others.

https://wordpress.org/extend/plugins/quick-post-widget/ plus others listed (check if updated to current WP version) in http://wpmu.org/8-wordpress-plugins-that-enable-posting-and-editing-from-the-front-end/

It’s not that the activation key is being “lost”. It’s that the user has already been activated, and the error being thrown by WP/BP (“provide a valid key”) is extremely unhelpful. It will be improved in BP 1.3.

Just instruct your users to log in with their username and password. They should find that their accounts are fully functional.

BTW, another plugin to help with activation is https://wordpress.org/extend/plugins/unconfirmed

@v_andreev

There’s also this plugin that’s supposed to work with BP: https://wordpress.org/extend/plugins/wp-activate-users/
And the code snippet in this thread works very well (I’ve used it): https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/get-non-activated-users/

I think you need to fix WordPress before you use BuddyPress. I am assuming your host has disabled ini_set; research into if you can re-enable it.

@Shazar

Joining a site running Buddypress can be as simple or as convoluted as you want to make it for potential members. There are quite a few plugins that can be implemented for captchas; authentification via other networks like Facebook, Google, etc; profile synchronization with other networks; custom login pages and much more. An example of the basic BP account creation process can be found on one of my sites here: http://buddylite.com/register/

The only thing I’ve added to the default registration process on BuddyLite is a simple math captcha called Buddypress Humanity: https://buddypress.org/community/groups/buddypress-humanity/
You can see a working example of one front-end post solution called TDO-Mini-Forms on the same site here: http://buddylite.com/buddybuilder-style-submission/ and the end results here: http://buddylite.com/category/custom-buddybuilder-styles/
You’ll need to login as a test user to see the form though… user = buzzer / pass = hellobirdie

On another site I’m currently working on, you can see an example of another front-end post form called Quick Post Widget: https://wordpress.org/extend/plugins/quick-post-widget/
See it here: http://kwitterz.com/share-your-thoughts-with-all-kwitterz/
Again, you’ll need to login… user = pjohn / pass = gollysarge

Hope this helps to get you started!

Make sure the .htcaccess file is at the root of your WordPress installation at that it has permissions of 644. Also, make sure Apache is enabled to do the URL rewrites that BuddyPress requires: http://www.lavluda.com/2007/07/15/how-to-enable-mod_rewrite-in-apache22-debian/.

> but why does BuddyPress think it’s not the case that a user should redirect to their info?

That’s just the way it works. By default, the BuddyPress front page is not the user’s profile page.

> Is there a way to code this, without getting into BuddyPress and later regretting it. I don’t want to use anymore plugins.

You can either edit/create bp-custom.php in the plugins directory or use a plugin that someone has created like bp-profile-as-homepage. If you look at the code for this plugin (one short php file), it is very simple. It taps into a wordpress hook to add a check to see if the user is logged in and if so whether the current page is the front page. If it is, then it redirects to the user’s profile page. That seems to be what you want.