BuddyPress.org

Greeeeeat news… The one that i was waiting for

So now, can i start using that new architcture ? how ? do i have to download the last build from the trac ?

Thx !

Sounds good! But sucks for existing theme developers (like me) who have customized the skeleton theme a bit!

Theme conversion takes time… but the future benefits outweigh the negatives

absolutely great news ! I think this will make customizations easier ?

Thanks a lot to all BP-developers !

Can we have a default theme code snapshot?

Once version 1.1 of BuddyPress is released, the Skeleton Theme that is currently bundled with BuddyPress (up to version 1.0.3) will be discontinued. Instead, BuddyPress will adopt the parent/child theme architecture that WP 2.7 made possible.

Learn more about parent/child themes in WordPress.

When you run on the bleeding edge, you have to accept the changes!

The BP themes that WPMU DEV currently provide are are not designed with the parent/child architecture in mind. You need to talk with them to get support.

Details About the New Theme Architecture

With BuddyPress version 1.1–which will be officially released in the next several weeks–there will no longer be bhome and bpmember themes. Instead, BuddyPress will adopt the parent/child theme architecture that WP 2.7 makes possible.

Backwards compatibility will remain for a while for those that want/need to use the old theming architecture. To use the old theme architecture, you need to keep the /bp-themes/ directory. Place your old member themes in there. BuddyPress should override the new theme architecture in favor of the old one if you have a /bp-themes/ directory. However, please note that support for the old theme architecture will eventually be phased out. You will eventually need to update your themes to a parent/child architecture.

Learn more about parent/child themes in WordPress.

1. you should use the latest stable version (1.0.3)

2. If it’s a WPMU DEV theme then you should probably talk to them in their support forum.

Hi Peterverkooijen, sorry you are struggling with this for a long time now. I’m not sure if you absolutely need this for bp1.0.3, but if you study the registration process of the upcoming bp, you’ll see it is much easier to manipulate registration data at a theme level.

It might be best worth your time to study the new code and wait a bit longer. Or work with trunk if you are developing.

This will be super easy in bp1.1 as the whole registration page is themeable, so you can easily comment out or delete that section as it is off by default.

That’ what I do as in conjunction with the groupblog plugin, as groups do can create blogs at group creation, but not at user signup.

You’ll see, bp1.1 will be so much easier to theme.

PS. Sorry if this info doesn’t help you right now Thought I’d give you some hope for what’s to come!

Two questions:

1. Does this issue go away if you switch to the default themes that come with BuddyPress?
2. Are there any errors showing up in your log files?

Once v1.1 comes out in the next couple of weeks, this issue should be moot. There will no longer be bhome and bpmember themes. Instead, BuddyPress will adopt the parent/child theme architecture that WP 2.7 makes possible.

Backwards compatibility will remain for a while for those that want/need to use the old theming architecture. But it will eventually be phased out.

Learn more about parent/child themes in WordPress.

You can try copying over the various functions you want to use into the bpmember theme’s functions.php file.

Well, you’ll need some PHP, CSS, and WP theming knowledge to modify WP themes. Here’s a helpful link to get you started with WP theme designing.

Are you using the new parent/child theme architecture or an older member theme located in /bp-themes/?

I would like to bring this topic I posted yesterday to this thread’s attention: https://buddypress.org/forums/topic/how-to-use-bphome-functions-on-bp-member-pages

TDO forms plugin may help you or take a look at P2 theme

Ok Kunal replace this part:

<?php

if ( function_exists('wp_logout_url') ) {

$logout_link = '/ <a href="' . wp_logout_url( $bp->root_domain ) . '">' . __( 'Log Out', 'buddypress' ) . '</a>';

} else {

$logout_link = '/ <a href="' . $bp->root_domain . '/wp-login.php?action=logout&redirect_to=' . $bp->root_domain . '">' . __( 'Log Out', 'buddypress' ) . '</a>';

}



echo apply_filters( 'bp_logout_link', $logout_link );

?>

With This:

<a href="<?php echo wp_logout_url( get_permalink() ); ?>" title="Logout">Logout</a>

And that should solve the logout issue.