BuddyPress.org

Testbp runs unmodified versions of BuddyPress and bbPress development versions

when you use bbPress with BuddyPress default theme it has the the same theme that is on testbp.org.

This article should help.

http://www.acousticwebdesign.net/wordpress/how-to-create-wordpress-3-navigation-menus-in-your-theme-or-plugin-code/

Just to clarify, the bbPress you’re referring to is the plugin, right? Because bp-default theme and BP themes in WP repo and premium do already add pages/style for internal bbPress forum bundled with BuddyPress.

What theme are you using? What are the links in your main nav at this time? Or, this might just be what you need http://www.nathanrice.net/blog/creating-a-blog-page-with-paging/ – with a reminder to delete spaces between < and ? and php ergo should be ` when you copy and paste from the tutorial

@gregfielding I know what you mean

As DJPaul mentioned here, child themes can declare and empty function to override parent theme’s function. Check out Boone’s solution – a proposed patch which works of course and is better IMHO.

You might have noticed that the link to stylesheet is no longer in bp-default theme’s header.php. Hence, you could either add the link to stylesheet in child theme’s header.php or enqueue main stylesheet ala bp-default theme.

Cheers.

That solution did not work for me. I copied the _inc folder into my child theme, and disabled Buddypress Template Pack.

The layout was then messed up, no doubt from missing CSS. I could Add a Friend, but it didn’t use Ajax. It just re-loaded the page. And trying to post a status update just leads to a 404.

If I enable Buddypress Template Pack, it tried to use Ajax for Add a Friend and Status Update, but neither work.

It might be your custom theme that’s not compatible or updated for BP 1.2.9. Change to bp-default theme.

I’ve got this error now as well. I activated buddypress and then activated the default theme BEFORE going through the buddypress setup wizard.

How can I undo?

You can see it:
http://townswell.com/

Thanks!

Tosh, please try my way, 1. use any themes of your choice 2. Enable BuddyPress Template Pack 3. Copy folder _inc from “/public_html/wp-content/plugins/buddypress/bp-themes/bp-default” into your theme directory

its work at my site indonesiabox.com and also otolover.com

Plugins are better because then you have options as apposed to only having what is in core. BuddyPress comes with a set of core components but each of these have hooks, filters you can plugin into and craft anything your coding skills can muster.

You can use the profile part or maybe you just need groups. Pick and choose what you need to make it work for you.

The BP template pack plugin is there to help you integrate with a regular WP theme.

Code snippets:

http://bp-tricks.com
http://blog.etiviti.com/tag/buddypress-hack
http://buddydev.com/category/buddypress-tricks/

My idea would be to use the body class:


.logged-in


For instance we have the following class and style for the padding:


body {
padding-top: 25px;
}


We could use something like this:


body.logged-in{
padding-top: 25px!important;
}

body{
padding-top: 0px!important;
}


This would be in the child theme and unfortunately requires some bunny killing by the use of !important as a dirty fix.

A ticket does seem sensible to me with a simple class change on if logged in like I’ve put there. Whilst we do need that padding there it just sticking with no admin bar probably isn’t best.

In the ticket / non hacky method I’d suggest it without the bunny killing code :


body.logged-in{
padding-top: 25px;
}

body{
padding-top: 0px;
}


Try copying the folder _inc from bp-default over to your theme folder.

I was posting on a StudioPress forum about their efforts to upgrade their Genesis Connect plugin for compatibility with v1.5 and asked about the recommended install process (uninstall/re-install). The answer in part was:

“There are BP 1.2.9 functions calls in GC 1.0.7 that are not in the BP 1.5 beta-2. If you leave GC 1.0.7 active and upgrade BP, you end up with call to undefined function errors both in the front end and in the admin area of your site.”

BP 1.5 seems like a major move and, from what I’ve seen as I begin to look at it, a very beneficial move. However, it also seems, from the discussion in this forum, to be a move with big impact in terms of plugins. I’m new here, but on that basis I have a question:

Would it have been possible or make sense to ease the transition in some cases by providing some adapter functions that would translate old replaced functions with re-directions to their new counterparts? The old functions could then be identified as deprecated and removed at a later date, but in the immediate horizon some plugin modules might continue to work rather than needing to be modified or abandoned? Simply dropping stuff without fair warning seems drastic.

It might not be possible in all cases, but it might help with the transition. I know a lot of people want to move forward to the new v1.5 and this type of code strategy might help.

Just a thought.

BTW – I’m beginning to play with beta 5029 and it looks fantastic! Great job … you guys did a lot of good work!