BuddyPress.org

Make sure the code is in bp-custom.php and between the php tags

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

Moving your files under a folder in root of theme as either ‘community’ or ‘buddypress’ with the folder structure as seen under BP’s bp-legacy folder will allow you to overload all the templates to be used by BP first if found in preference to it’s own copies with the benefit of using the bp functions file and other assets styles js both of which are also copyable to your theme, but best to leave all but css under bp control, however theme compatibility was made as flexible as possible by design and you can move the whole thing i.e functions.php and create a new instance of the theme compat class referencing your own paths and files etc.

When you had your BP files directly in the theme root you were effectively telling BP that theme compat mode was disabled as it’s setup to run a check for files in certain paths and bail out of further theme compat setup, this is a tricky area though and the best advice is to work with theme compat as really there’s no good reason not to.

The two articles – which I think you have read already – are a good reference, be sure to read the second one that goes into more depth on the extended template hierarchy for BP templates.

Hi,
see if you have a folder named “plugins” in the wp-content/languages/ directory. If yes, you can put the buddypress po/mo there. This folder content has priority over “languages” content.

FYI, the file who make translation possible is not the po, but the mo file !

Hi @moonhopper

1/ Did you make a backup of your database before upgrading to BuddyPress 2.0 and creating the network ?
2/ Is it a live website or a dev one ?
3/ Can you check into the usermeta table of your site if for the problematic users you have a meta_key ‘activation_key’ with a meta value or not ? If so in the users table are these users having a user_status set to 0 ?
4/ What is the name of the theme ? Is it available on WordPress repository ?

@vayu @astarina, you may want to look into a theme called dokan, it’s a multi-vendor marketplace based on woocommerce. though i am not too sure about the buddypress integration, this may be possible for the author to add if demand or price is strong enough 😉

BuddyPress uses cookies for globals. You will need to sync those accordingly.

I *JUST* solved my issue by updating the outdated buddypress.css — but I don’t have the spam submit button issue. I’ll have to test that. I was getting double posts regardless everywhere a comment was contributed.

-Nick

I’ve been suffering the same issue. WP 3.9 / BP 2.0
A lot of users willing to sing up and post have been suffering this issue.
No fix posted yet.

I always get a double post, on comments/updates/anything involving a textbox in BuddyPress.

Also get a page refresh anytime I attempt to comment in the activity feed when “Everybody” filter is enabled.

Did you manage to fix your issue?
Any insight would be great!

OK, Looks like this is a problem caused by NextGen Gallery. Noted here:

Redirects to forum from group home (BuddyPress)

But still not fixed with NextGen Gallery V2.0.63 – 04.29.2014

> Should I remove all BuddyPress files in the theme template?

Try that.
We don’t know anything about your theme.
BP treats all themes the same, premium or free.
But since BP 1.7 (?), theme handling has changed.

Rather than try to ‘fix’ all those issues, imo. your time would be better spent switching to a new theme. It’s an opportunity 🙂 And will probably take less time that puzzling out all those issues.

But I’m not a theme expert; perhaps one of those folks will provide a more informed suggestion.

@xyhavoc

Just a quick follow up to inform you, i’ve read your discussion with @boonebgorges on 5603.
I’ve attached an alternative patch to the ticket, it would be great if you could test it.

Thanks again for your feedback.

My bad, I’ve just realised that wasn’t the solution…

I had to add the code in this function

xprofile_sync_wp_profile

in

wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-screens.php

I’m not sure why it doesn’t work in the bp-custom.php file…

@noizeburger Thank you for sharing this – it’s helped me out greatly.

I might just add to anyone else who’s going to implement this as I’d spent about four hours trying to figure out why it wouldn’t work for me initially.

add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 10, 1);

The number 10 states at what point the function should be called. This should work in most instances but I am using a theme with additional buddypress functions built in.

I had to set this to a higher level, meaning it gets executed later on in the process. At least I think that’s right. Anyhow, once I’d changed mine to

add_action( 'bp_core_signup_user', 'custom_bp_core_signup_user', 13, 1);

It worked fine!

It’s worth reading this.

https://codex.wordpress.org/Function_Reference/add_action

Thanks again

I’m guessing I’ll have to use a hook of some kind to accomplish this

You’re right. But the hook would be supplied by the Amen plugin. You could start by asking the plugin’s support if one is available. I’m guessing here but it will probably be called something like after_submit_prayer_request.

Then you’d build your own function which you can ‘hook’ on to the ‘after_submit_prayer_request’ hook (don’t forget I’m guessing at the hook name).

Your function would simply add an item to the BP activity stream and will look something like this:

function add_prayer_request_to_stream() {
    bp_activity_add( $args )
}
add_action( 'add_prayer_request_to_stream', 'actual_hook_name' );

Note: This won’t work until you have the actual hook name and have supplied the $args as an array that describes the activity item you’re creating.

See here for more info on the bp_activity_add() function

bp_activity_add()

Did you ever resolve this? I’ve just activated BP in wordpress site using the weaver II them and am having a similar issue. Everything seems to work but I never see an avatar and continually get this error message: Notice: Undefined property: BP_Groups_Group::$avatar_thumb in /homepages/24/d463872728/htdocs/APP/wp-content/plugins/buddypress/bp-groups/bp-groups-template.php on line 526. I’ve looked at the code and it’s not obvious to me what this means.

older downloads:
https://wordpress.org/plugins/buddypress/developers/

open a ticket:
https://buddypress.trac.wordpress.org/

@krazy-kat – Thanks for catching this bug.

A workaround in the meantime is to turn on the “Activity Streams” component.

To do this, login to the WP admin dashboard and navigate to “Settings > BuddyPress”. Check “Activity Streams” and save.

We’ll fix this bug up for v2.0.1.

Take a look at this article from the BP Codex on the Template Hierarchy:

Template Hierarchy

To summarise, you’d create a folder called /buddypress/ in your theme’s directory. Then a subfolder called ‘members’. Then a file called ‘index-register.php’. You should end up with:

/buddypress/members/index-register.php

Your register page’s code will go in that file and any customisations you make will take effect.

Please see the ticket that r-a-y referenced.

You can patch the file using the changeset:
https://buddypress.trac.wordpress.org/changeset/8305

Or wait for the release of BP.2.0.1

Hi @localiseorg

Socialise (sitewide activity assigned to this)
– Members (members directory assigned to this)
– Groups (groups directory assigned to this)
– Forums (bbPress forum root assigned to this)

Have you tried using a wp_nav_menu instead ?

I think, if i was in your situation, i’d make a wp_nav_menu with your different pages.. It could be “home”, “blog”, “socialise” for instance. And from the wp_nav_menu WordPress UI, i’d attach the Members/Groups and forums as submenus of Socialise.

Then concerning the Socialise title that is “Sitewide Activity”, i’ll begin to edit the activity page changing the title from Activity to Socialise and use a little code like the following:

function change_activity_directory_title() {
	buddypress()->activity->directory_title = buddypress()->pages->activity->title;
}
add_action( 'bp_activity_setup_globals', 'change_activity_directory_title' );