BuddyPress.org

Ah right. I’d copy/pasted that from a standard WordPress theme. Thanks for the correction.

Actually you’d need to use

bloginfo('stylesheet_directory')

template_directory gets your parent theme directory, while stylesheet_directory gets your child theme directory

To be honest, there really isn’t one, at least not on paper. I can’t say that WordPress has one either.

It isn’t really about how the pieces fit, as much as it’s about how you adapt them to fit your needs. This is similar to WordPress, where it started as blogging software but people bend it around backwards to work in other ways.

Without sounding too much like a broken record, the about page sums up almost all of the functionalities of BP; none of them are more important than the others. It’s up to a good theme designer and code slinger to bring those components out and emphasize their importance to a community website.

Out of the box, BuddyPress is designed for all elements to be created equal. Groups are no more important than friends are no more important than activity are no more important than forums are no more important than directories are no more important than… You get the idea… It’s up to a good theme designer and a great developer to make the functions of BuddyPress pop-out and turn a WordPress site into a meetup.com or linkedin.com.

All of the elements exist in the core and in external plugins to do it, it just has yet to be done.

Every wordpress theme needs at least a style.css file, bloginfo(‘stylesheet_url’); tells the theme to get it’s style.css file. If you want another one, change the style.css or just add another stylesheet underneath your style.css sheet.

If your totally new to WordPress, try downloading a theme from the wordpress theme directory on wordpress.org and see how it’s made. Maybe then you’ll have a better understanding on how to do things in wordpress, like calling multiple stylesheets.

Here’s an example.

<link href="<?php bloginfo('template_directory'); ?>/css/style2.css" rel="stylesheet" type="text/css" />

Yes, that line gets your current theme’s style.css file. In buddypress’s case, it’ll get the bp-sn-parent style.ccs..

There is a template called optionsbar.php in the parent theme… but it just calls a function of course… bp_get_options_nav(). So I’m not sure you can reorder them. Maybe someone else knows.

I don’t believe the BP theme as a template hierarchy. All of the template in the parent theme are required. I would say.

The bp-default theme is a “child theme” of bp-sn-parent theme, and you copy the bp-default theme and rename the theme folder to e.g. mythemename to make a child theme of your own. It’s not easy. If you have strong CSS foundation and Firebug, this process will take a few hours to tweak if you already have a design in mind.

https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/ Plus google “create wordpress child themes” or check out ” free BuddyPress child themes”

Btw, you can download latest BP 1.1.3 already

copy the footer.php to themes/bp-default and edit that one, your modification will be kept in the future when you upgrade the parent theme.

rcmisa – looking at your website you are using the default theme, so the footer.php will be in wp-content/themes/bp-sn-parent.

I’m getting the issue with the latest trunk and a completely virgin default theme. Activation works fine without BP active. But I’m not complaining. I’m running the ‘bleeding edge’… so I expect bugs.

That’s because “default” is a child theme. It inherits it’s footer from it’s parent theme. To create a custom footer for you child theme… just copy the footer.php file from the parent into the child. The child footer will override the parent.

Yup. Per buddydress.com notes the theme was good to BP 1.0 only. Change back to bp-default theme to get home page back to normal.

I believe those themes do not work with the latest buddypress.

@member11

The theme I’m building is a parent theme, so I put the code I posted above in the single.php file. This is the page that shows a single blog post.

I’m having this problem with the latest trunk as well… using the default theme. But I guess that goes with the territory.

I’m not entirely sure how to handle the removal of the wire yet. For now it remains, but with no support in the theme.

There are a few options:

1. Remove it completely and provide it as a separate plugin.

2. Deprecate it somehow and allow people to load it if they need.

3. Leave it as it is but turn it off by default.

I believe this project came to a halt 3 months ago. I’m planning on releasing a few cool buddypress themes soon, so sit tight.

@ illwill79: If you need help with something, pm me.

Your home page style is looking very nice. I too am working on creating a home page style, but am running into issues. I’ll be following your progress.

Aye, my eyes, it hurts…

the usage of the site is good… good topic… but the theme, aye!