BuddyPress.org

I am also interested in this question.

Thankfully for us both, this isn’t a debate.

For various reasons related to our WordPress trademark, we ask if you’re going to start a site about WordPress or related to it that you not use “WordPress” in the domain name. Try using “wp” instead, or another variation. We’re not lawyers, but very good ones tell us we have to do this to preserve our trademark. Also many users have told us they find it confusing.

If you already have a domain with “WordPress” in it, redirecting it to the “wp” equivalent is fine, just as long as the main one users see and you promote doesn’t contain “WordPress.”

“WordPress” in sub-domains is fine, like wordpress.example.com, we’re just concerned about top-level domains.

We’ve told this to anyone who has ever asked us, we just wanted to make it public so more people could be aware of this policy.

I applaud your efforts, and hope your intention is at least to make the theme available publically.

I’m keeping this topic open for now, but it’s on my watch list because it’s already breaking some rules. If it gets too rowdy in here I’m locking it up.

May want to read this…

Domain Policy

Same goes with WordPress as well.

In response, good job modifying the theme colors. In my opinion the forums could still use some work (margins on the sides need 20px), and the missing BuddyBar at the top urks me.

Also, and this may be a repeat suggestion, but when upgrading, you’re going to want to BACKUP and DELETE the old files, all of them EXCEPT your wp-config.php file. That file you do NOT delete and keep where it belongs.

1. Upload WPMU, visit wp-admin, and make sure it’s running the way it should be.

2. Upload BuddyPress per the install instructions, visit wp-admin, make sure it’s running the way it should be.

3. Reinstall plugins and custom themes.

The reason for the delete is because of all the file locations and names that have changed around since RC1. If you have copies of old files lying around, say in mu-plugins, etc… That will gum things up too.

We’re working in the dark here Michael. What is your installation config like? subdomain or subdirectory? Windows, Mac or Linux? Shared or dedicated hosting?

You have the latest mu 2.7.1 branch and the latest bp trunk installed correctly

You have deleted bp completely from /mu-plugins and installed it in /plugins/buddypress

You have your member theme in /wp-content/bp-themes

You have activated sitewide the buddypress plugin

Your wpmu install works perfectly. You can create new blogs and post to them.

You do not have *any* other plugins running at all.

After all the above is ‘yes’ you get a white screen when visting any url in bp or wpmu? You have to be getting errors. Make sure that your php.ini file is configured to report errors and you are looking where it’s reporting.

Is this the same host as the bp install that is working?

Are you using a custom theme?

If this occurs with the standard theme, then the error is probably because you have installed the BP themes incorrectly.

I came here because I want such a theme but a stable core, or a one click mu/bbpress/bp install is my first choice. Go for it!

I’am currently working on a matching bbPress theme for BuddyPress … But, it only fit my (tweaked) theme for BuddyPress

The forum is up and running, but the theme is still in development

The color scheme i use can be seen over here:

http://wordpress-blog.nl

Ehy Jeff look here wp-content/themes/buddypress-home/register.php

if you’ve a customized theme copy register.php and activation.php from /themes/buddypress-home to your theme

The bbPress template is PAINFUL to modify. Doesn’t work the same was as WordPresss.

I’ve found though that the blank theme available from

http://www.refueled.net/blank-themes/

make creating a matching theme so much easier.

Check them out.

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

@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.

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

Great job on schmink-tipps!

You know, there’s got to be some file somewhere that gets written to (or multiple files), when you configure widgets. Basically, all I need to do is automatically put that file into each new member’s blog, and I should be done. The way things are right now, the home theme works fine for user blogs, but the widgets aren’t configured.

So these are the steps I’m thinking would be easiest to follow:

1) Figure out where the widget configuration gets stored

2) Configure the widgets

3) Figure out how to get a pre-configured theme for new members (by copying certain files or writing a script or I don’t know what)

Answers? Helpful? Goofy?

Best,

Dainis