BuddyPress.org

I had the same problem after updating BP. Everything works fine now.

Check this post:

https://buddypress.org/forums/topic.php?id=1994#post-10705

Actually, those instructions apply even if you have customized just the home theme or the member theme. Even though it does not explicitly say so, if you have customized your home theme, you should copy over the new functions.php file from the buddypress-home theme folder in RC2.

There are also some changes to the code in the header.php file that you may want to make in your custom header.php file. In fact, for good measure, you should copy over any of the files from the new theme directory that you have not hacked in your custom theme.

Finally, just in case, have you read this thread?

https://buddypress.org/forums/topic.php?id=1661

https://buddypress.org/forums/topic.php?id=1109#post-5165

@Socialpreneur, I didn’t design it — Tim Bowen of Creative Slice did the visual theme modifications. But thanks! It’s a strong community and BuddyPress has been the perfect fit for us.

At this point in development, will i need to develop one theme for my buddypress and one theme for my bbpress? so that there will be no difference between the two?

In short, yes.

If you want your site-wide forum theme to look like your BuddyPress theme, you’ll have to customize both themes.

Hally-

wp-signup.php is a WordPress Mu file, not a BuddyPress file. Look within the directory you’ve installed WPMU.

Scotm-

Did you follow the instructions for custom themes at the very end of Andy’s first post here: https://buddypress.org/forums/topic.php?id=1994#post-10557 ?

As others started the upgrade process, and had certain issues, he made changes to the instructions. Depending on when you upgraded, you may have missed this.

Read this thread: https://buddypress.org/forums/topic.php?id=1661#post-8547

First, we need some basic information:

1. What version of WPMU and BuddyPress are you running?

Until we have that information, perhaps this thread will help: https://buddypress.org/forums/topic.php?id=1661#post-8547

Ah — you mentioned RC1. Then yes, the BuddyPress plugins would be in “mu-plugins” still.

Write in new language to msgstr within buddypress.pot and save as buddypress-spots.mo

Make sure you are creating the MO file from a PO file, which is in turn a copy of the POT that is bundled with BuddyPress.

Your “bp-languages” directory should look something like this:

buddypress.pot

buddypress-mysite.po

buddypress-mysite.mo

If you have trouble editing the POT or PO in a text editor, you can use special software also — see https://codex.wordpress.org/Translating_WordPress and look for “Translation Tools.” In my opinion those are overkill for this type of thing, though.

I had to put BP-dev plugins inside /plugins/buddypress/

however, not all of them work now…. my profile widgets do not show up in the “show widgets” area of the appearance>widgets>

the “widget area” shows up on the profile page, but i cannot add any of the widgets in

appearance>widgets> from the wp-admin backend

should i just add these sidebars to the functions page?

am i missing something? are they in wrong spot?

@Seobrien — wrong instructions, maybe? Follow my link: https://codex.buddypress.org/developer-docs/customizing-labels-messages-and-urls/.

There is no mention of “mu-plugins” in the page, and you have to make sure the “spots” part of the file name to match your own site’s nickname or label.

Having worked through the thread, my understanding is that this is the set of directions to follow in RC1 yet it failed to change anything:

1. Write in new language to msgstr within buddypress.pot and save as buddypress-spots.mo (wp-content/mu-plugins/bp-languages/buddypress-spots.mo)

msgid “Group Wire”

msgstr “Group CHANGED”

2. Create custom file bp-custom.php (wp-content/mu-plugins/bp-custom.php) as such:

<?php

define( ‘BPLANG’, ‘spots’ );

if ( file_exists( BP_PLUGIN_DIR . ‘/bp-languages/buddypress-‘ . BPLANG . ‘.mo’ ) ) {

load_textdomain( ‘buddypress’, BP_PLUGIN_DIR . ‘/bp-languages/buddypress-‘ . BPLANG . ‘.mo’ );

}

?>

What am I missing?

Follow-up: I’ve posted a better instruction set with code examples: Customizing Labels, Messages, and URLs.

For anyone interested in customizing labels and messages (like renaming “Wire”) for example, I’ve posted a full instruction set with examples to the Codex: Customizing Labels, Messages, and URLs.

Ezra, Seobrien, Timothy, and others interested in customizing labels and messages — I’ve posted a full instruction set with examples to the Codex: Customizing Labels, Messages, and URLs.

Looks like this was fixed in Changeset 1157. Therefore, the bug still exists if you’re using RC1.

You have two choices:

1. Either upgrade to the latest trunk (as Burt says) following these instructions: https://buddypress.org/forums/topic.php?id=1994

2. Or, wait until WordPress MU 2.7.1 is officially released and an official BuddyPress RC2 zip is available.

@Socialpreneur

I my self is new to buddypress and its template, I have however found out that side-wide.css REALLY means side wide, meaning, all members pages are affected aswell,

As an example, if you add the css \”widht:900px;border 1px solid #000000;\” to you body through side-wide.css all members pages will be 900 px wide and have a 1 px border around them.

If you just want to tweek the buddypress template and not change it completely, put the extra css in custom.css. This well give you the same effect but not effecting you member blogs.

You do need to upload the custom.css to both the home theme and member theme for the changes to work in both templates.

Hope it helps.