BuddyPress.org

Hi I am not sure what I did wrong and its not working properly…

I got the errors everything after i post a forum topic.. The new translation is done but I got this error….

Warning: Cannot modify header information – headers already sent by (output started at /home/footheal/public_html/commandoclub.net/wp-content/plugins/bp-custom.php: in /home/footheal/public_html/commandoclub.net/wp-includes/pluggable.php on line 897

Please help.

@siken

Did you remember to remove the code you added to wp-config.php as per the plugin instructions?

`define( ‘BP_DISABLE_ADMIN_BAR’, true );`

You’ll need to be running the development version (trunk) of BuddyPress for it to work, or wait for a beta.

32Mb probably won’t cut it; running any kind of busy BP install on shared hosting is going to be dodgy. I did so for a while on my Dreamhost account before I went for a VPS and it was fine, but you may not be so lucky with other hosts.

I would avoid Media Temple. Nice site design; not such great service, is what I’ve been told.

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.

What did you do, Iamyeti, to fix the .htaccess file?

@BrainiacWebDesigns

Glad it helped

My partner Ron wrote it. The post linked to our blog. Have you tried it on a test site?

You can certainly replace the default avatar picture, either with a bp_default instruction in wp-config.php or by adding a new function (into functions.php). If you wanted to achieve a random selection from a pool of avatars then I suppose you would need to write some php of javascript to intercept the avatar display and randomly select from an array.

I’ve not seen anything off-the-shelf for BuddyPress, so you’d probably need to adapt a script and hook it into BuddyPress.

There was a script I used a while back in a Social Engine 4 implementation that basically presented users with choice of standard avatars on signup, which would be a better way of implementing this, since it’s important to encourage users to personalise their profiles which leads to greater engagement.

Here’s an example of what I mean – http://webhive.com.ua/store/product.php?id_product=36 – but I’ve not seen this for a BP environment.

@naved, post a link to your website please.

@DJPaul this is why I have raised the matter again check your emails when you have a moment, we may not be aware of any issues but that doesn’t mean there aren’t any.

There are no known security issues with BuddyPress 1.2.x, or BuddyPress 1.3. Promoting scare web pages help no-one.

@naved

Rather than editing core files and losing those changes when you upgrade Buddypress, the safer route is to create a language file for customized messages.

https://codex.buddypress.org/extending-buddypress/customizing-labels-messages-and-urls/

@janismo Yes I know about that sign and am discussing it with one of the core mods.

@BlueInkAlchemist I have actually just finished upgrading the plugin to work with WP 3.1 and have it running on BP 1.3 trunk and it looks to be ok but I’ll need to contact Rich! about updating the repo version.

@BrainiacWebDesigns

For your sidebar widget issue, @hnla is right: contacting the theme author is probably the best route.

For the 503 message quoted above, that looks like suspiciously like one I got recently on one of my sites, which turned out to be a setting in the s2member plugin. If you’re using that plugin (and I suspect you are), check the “Unique IP Access Restrictions” setting under “s2member” > “General Options” in your WP backend. If you have that setting set to, say, 5 different IPs per customer, and more that 5 nice folks on this forum try to help you by accessing your test account (from different IPs obviously), the warning will be triggered. If you don’t want that warning to display to your site members who may use several different machines to access your site, you can set it to a higher number or disable it altogether (“Allow Infinite IPs”).

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.

It’s a well known and long standing issue.

thanks this fixed my problem