BuddyPress.org

I always use the files from
/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress

And would put them in:
/wp-content/themes/BuddyEnglish/buddypress/

no. the secondary blog setup is only if you are running wp multisite

You could also try Welcome Pack by Paul Gibbs – it allows you to send a welcome email and also customise the various more emails BuddyPress sends out:

https://wordpress.org/plugins/welcome-pack/

I experienced this exact same problem on a site I recently upgraded from an older version of buddypress/bbpress. Private group replies were available in users’ activity stream to non-logged in users even. I turned off all plugins with no affect.

This can’t be done using BuddyPress as it comes out of the box. You’d need a plugin or some custom code which allows users to save a image file to their profile data.

You can setup a network and use bp-multinetwork (free plugin – search wordpress.org). So you have the possibility to setup two different bp-networks with one common userbase. To hide things from logged out users there are a few plugins available (search buddypress.org).

You could explode to an array and then loop thru it.

But the default is to return an array, so just remove this
$multi_format = 'comma'

Then use a foreach loop to generate some markup that uses br or li tags.

@dexter86re
I don’t see the users name twice in the head. Maybe you need to press ctrl+F5 to refresh. This really isn’t a BuddyPress issue, as I only see bbPress is installed.

@kingdgm

The BuddyPress Jobs Board is the best place to start:

BP Jobs Board

Hello,

check the server error logs may be you find something there…

Thanks

Hello,

I can give you reference for good WordPress developers who can build plugins and do any thing in WordPress.

[edit – @wordpress_bipin do not post link to site which uses WordPress in the domain name https://wordpress.org/about/domains/ ~~~ Mercime]

Avatar upload fails

We’ll see more patches from you in the future, yes?

@mercime I hope so.

You should be able to run a tortoise checkout with this url.
https://svn.buddypress.org/trunk

@hnla For the patch I submitted, I had used https://buddypress.svn.wordpress.org/trunk/ Should I use https://svn.buddypress.org/trunk instead? Do the 2 URLs point to different resources?

Closing thread. Duplicate of:
https://buddypress.org/support/topic/warning-message-when-activated/

Please don’t open more than one thread on a topic.

@henrywright-1
I think on balance I would tend now to favour going the theme compat route, as the process best to follow in all theme/site building respects, we added extended capabilities with the template hierarchy which make it more useful and the templates and styles were updated and improved.

But the other approach is perfectly valid and leaves full templates directly in your control.

Personally I like the the ability, though, of being able to neatly segregate BP templates under one root dir /community/ or /buddypress/

As for the js being the reasoning remember that both approaches essentially use copies of the same file/s so you still get those either way, one thing I’d like to see and may propose is the main js & ajax files being centralized as bp assets that both approaches could access rather than maintained separately in the theme folders – although that is the place they ought to live really.

This whole question of approach taken is one I’ve raised as there are confusing aspects and I want a codex guide that outlines the approaches on offer and brings some clarity to making choices, which we’ll pencil in to the new guides once Codex is straightened out.

@sooskriszta
You should be able to run a tortoise checkout with this url.
https://svn.buddypress.org/trunk