BuddyPress.org

If you already have a child theme in use then that’s great you do not need to repeat that step, you will use your child theme to hold copies of various buddypress files so that you may modify them safely.

Please always check the documentation that is available as we have some guides on tackling this aspect of overloading BP files to child themes, these guides will explain how to proceed.

Theme Compatibility

If/when you have further questions do post back to this thread.

Hi @richonbp

(1) A combination of PHP, JavaScript, jQuery and Ajax is the usual.
(2 – 4) Depends on your requirements
(5) Usually a combination of WordPress and BuddyPress to begin with. Then any plugins you need. You might also want to choose a theme

Hope this helps!

When you’re ready to go ahead, try posting your requirements and some contact information on the BP Jobs Board – there are some good programmers around that check on that forum regularly.

AFAIK, no-one on the BuddyPress core team has tested BuddyPress extensively on HHVM. Also, we do not check our unit tests on HHVM.

Informally, I think our position is along the lines of “once HHVM is officially supported in WordPress core, we’ll officially support it in BuddyPress core.” Note that there’s a difference between “works well” and “officially supported”.

However, if people like yourself want to run BuddyPress on HHVM and report any issues to us (or help us debug and fix them), we’d love that.

I’m no expert in jQuery but I think buddypress.js uses jq to reference jQuery. And it’s perfectly OK to do that if you do something like this var jq = jQuery; (which buddypress.js does). I don’t think the problem is with buddypress.js. Instead, check jQuery is enqueued on your homepage. And also check you’re enqueueing it just once.

A good place to check out the BuddyPress code is on the GitHub repo. Signups are managed by the BP_Signup class.

You can use this loop to print avatar images with names.

Check this link. http://webdevelopmentgyan.blogspot.in/2014/08/buddypress-show-member-avatar.html

Accepted:

Use the do_action hook in function friends_accept_friendship in this file:
buddypress\buddypress\bp-friends\bp-friends-functions.php

function my_accepted_function( $id, $user_id, $friend_id, $friendship  ) {
  // do something
}
add_action(''friends_friendship_accepted', 'my_accepted_function', 1, 4 );

Removed:

Use one of the 3 do_action hooks in function friends_remove_friend in this file:
buddypress\buddypress\bp-friends\bp-friends-functions.php

Which hook you use depends on what you want to do.
Create a separate function to hook to; something like ‘my_remove_function’.

salut @syl20g,

check the permalinks settings, /membres/ is in reality /?page_id=3549

Find more about BP install in french on http://bp-fr.net
or on BP codex 😉

hi @carlenb,

there is no buddypress forum. BuddyPress use the bbPress forum plugin, and once it is installed you can opt for a global forum or a group forum or both.

worddraw is outdated.
drawblog mentionned in the topic you linked is for wp comments and according to support doesn’t work with ios.

Perhaps try this one: https://wordpress.org/plugins/deviantart-muro/

@daneraid
please read here and give more details

If you are on a local install, you cannot login yourself as super-admin and also for a user you added.

If it is the case, revert back to original install of BP and use this plugin. This will literally fill your site with users, friends, groups and all kind of other activities.

Hi @jungmook,
it’s a bit difficult to answer a such wide open question in one post. So very shortly:

For a multisite installation of WP with Buddypress, do all the sites in the network of sites share the same user base?

Yes. There is only one wp_users table in the DB. And by default all registered users are network users.

Can WP multisite with BP be easily configured to work the same way (and yet let each site have its own separate forums and groups)?

Yes and No.
BuddyPress on multisite runs for the whole network. If you’re not comfortable with WordPres and never used BuddyPress it’s not easy at all, because you have to learn a bit first.

If you’re comfortable with WP, it’s relatively easy because BP is “only” a plugin and it works like a plugin.

And if you’ve never worked on a network (meaning a multisite) it could be complicated at first because you probably don’t be familiar with things such as activating a plugin on the main site and not for one of your network site, or vice versa.

I encourage you to read attentively the codex, show some videos about wordpress multisite and get the one or other tutorial you can find on the web.

Some reference

Installing Group and Sitewide Forums

http://www.wpbeginner.com/wp-tutorials/how-to-install-and-setup-wordpress-multisite-network/
http://premium.wpmudev.org/manuals/wpmu-and-buddypress-installation-2/

see here the answer from @shanebp.
He listed all notification instance in the po file

Maybe you have an idea what that could be?

You give the answer: once translated to German and once not.
Guess if something is not translated, you can’t see it. 😉

It could also to be that if you added the header infos to your po, that your translation plugin found immediatly some forgotten strings or new ones and added them, so you saw those unstranslated strings.

I suggest you to update the po file from the source using poEdit locally, for example from within bp-languages/buddypress-de_DE.po, to ensure that you have all 1476 strings of BP 2.0.2

Once done, you remove the po/mo from bp-languages and put them into wp-content/languages/plugins/

Hallo @findolfin,

Effectively, many peoples are claming about de_DE translation issue.

As the german translation for BuddyPress awaible on GlotPress is only translated to 52% (58% for 1.9!), the only other source to get po/mo files is deckerweb who provides 2 versions, Du and Sie version for BP 1.9 (latest in january 2014)

I downloaded the Sie version and opened the po. This file doesn’t contain any header information. So i guess gettext can’t read it correctly. And if you use this file it could be at the origin of your issue.

Here are the whole header informations, including the whole keywords list like _x which you need to add into your german buddypress-de_DE.po
Open the file with a text editor (notepad++ or similar) and paste it at the beginning of the file.

Once done, you must open the modified po with poEdit and save it again, to generate the mo file which is in fact the compiled format of the translation used by gettext.

msgid ""
msgstr ""
"PO-Revision-Date: 2014-08-08 09:45+0100\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n > 1;\n"
"X-Generator: Poedit 1.5.7\n"
"Project-Id-Version: BuddyPress 2.0.2\n"
"POT-Creation-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: de\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-Basepath: .\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop:1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;esc_attr__;"
"esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n"
"X-Poedit-SearchPath-0: ..\n"

Check this first and if it does not work, give feedback. And also theme name in case of. 😉

AFAIK, those plugins don’t offer front-end integration with BuddyPress. You/someone will have to build that.

Hi @csimpson,

the answer is on the codex (bp_parse_args)

Add this to your theme’s functions.php or into bp-custom.php

function bpfr_make_name_members_only( $retval ) {	
	//hold all of our info
	global $bp;
	
	// is xprofile active ?	
	if ( bp_is_active( 'xprofile' ) )
	
    // The user ID of the currently logged in user
    $current_user_id = (int) trim($bp->loggedin_user->id);
	
    // The author that we are currently viewing
    $author_id  = (int) trim($bp->displayed_user->id);
	 
	// user can see only his name && admin can see everyone 
	if ($current_user_id !== $author_id && !current_user_can('delete_others_pages') ) {
		$retval['exclude_fields'] = '1';	
	}
	return $retval;	
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_make_name_members_only' );

EDIT: this snippet does work only on BP 2.0+. Don’t use it with older versions.

Hi @heatherkirk

I’ve never used mqtranslate but there may be an alternative way to customise those strings. Check out the Customizing Labels, Messages, and URLs article which shows you how to set up a language file. Hopefully that’ll help?

Hi @rebhiadel,

2 solutions:
1) modifing the template in your child-theme
2) coding your own plugin

read on codex:
template (sort option)
coding

BuddyPress Groups Extras can do the job, but only in PRO version.
https://wordpress.org/support/plugin/buddypress-groups-extras

If you feel right to do it yourself, read this tutorial on the codex:

How to Edit Group Meta Tutorial

Hi @arpit2011,

read here:

Register and Activation Pages

and please, don’t jump in a post marked as resolved. Open your own if you have questions.

Hi @dolliv,

custom functions are generally added to one of these files:

functions.php

https://codex.buddypress.org/plugindev/bp-custom-php/

Hi Ajay,

I found your ticket on BP Trac just now and have posted a response:
https://buddypress.trac.wordpress.org/ticket/5787#comment:2

Let’s continue discussion there.

Thanks!