@andrea_r
I have successfully upgraded to 3.0, I´m running BP 1.2.4.1. And I have the basic twenty ten theme installed. However the bp functions are not working, its not listing “activity”, “members” etc in the menu. Instead the items are stacking at the bottom of my page. Am I missing something? 
I’ll give it another go hopefully over the weekend.
Ok, then I will just wait. Thanks for the reply
I’m owrking on this again tonight and have hit the headdesk part.
Brand new install, 3.0, network enabled. I added the BP template pack plugin and set it up on the default theme with the latest version of BP. Looks flawless, no child theme needed.
Local install: was mu, upgraded to 3.0. upgraded BP & the template pack plugin. Set it up on a secondary blog on the site.
It borked.
Reselected the theme, that was better. At least the admin bar was in the right spot. Now all it will show is the Members page when I click any link. *sigh*.
so! Anyone desperately waiting, please try the BP template pack plugin first. If it works for you, AWESOME. If not, hang on.
@andrea_r
Are you saying if I start with new install of everything, it should work with the BP template pack plugin?
I just fixed this last night. Go redownload it and try it. Install it in the theme folder and it should be fine.
Yeah, that’s a styling issue I’ll have to fix. 
Add this to the stylesheet:
ul.item-list li {
clear:both;
}
Thanks a lot. Now it works perfectly.
Let me know how it works Buddypress… I have a WP 3.0 Multiuser install with Buddypress 1.2.5 and I wish to have a network like WordPress.com. I need a common admin bar for all the network sites, so the users coming from the other sites can access to the network services (groups, forums, activity, pm, etc..) of the main site. So I need a unique template for all the sites. To do that, I cannot use the BP-Twentyten template but I converted the Twentyten template, using the BuddyPress Template Pack plugin. So now I have a template I can use on Buddypress based main site and also on the slave sites. The only problem is that this new template needs the BuddyPress Template Pack plugin to work. Actually I’m working on a test install, I need for the production install a common template independent from the plugin, but I have no coding skills to make it working. Can you help me?
You didn’t need to do all that work if all you really wanted was the admin bar on all sites across the network. the user blogs do no need a buddypress theme. the admin bar should show across all sites anyway.
Unfortunately it doesn’t work for me in the way you suggest. The admin bar didn’t show if I use the normal Twentyten theme for slave sites.
@marcogiustini – That’s strange – what themes are you using on the secondary sites? As long as the themes contain do_action( 'wp_footer' ), the admin bar should show up on them.
You mean that the secondary sites’ themes must contain do_action( ‘wp_footer’) ? Where?
In the footer.php file, which twentyten does have.
Strange it’s not showing though.
Per my comment on that guy’s blog, it’s not been built as a child theme, which is mad.
Child theme of Twenty Ten now added…
@djpaul so you want there to be only one buddypress theme?
@alanchrishughes, @djpaul is dead right, it should have been a child theme. I started looking at it before WP 3 was out & figured most wouldn’t have Twenty Ten installed so started it as a stand alone theme. It only took 10 mins to turn it into a child theme, should have done it sooner….
All others will be done as child themes where possible.
@thekmen I’m just one of the people that think themes should be completely separated from the plugin the same way they are separated from WordPress. Trying to reduce everything to one theme with a bunch of child themes is only going to slow down development and discourage people from appreciating Buddypress. I mean look how few themes there are, one theme with with a couple color alteration child themes and now people are excited just to be able to use the generic WordPress default.
I actually prefer this not being a child theme because I’m not a programmer and don’t know enough to write a theme completely from scratch, and this WordPress default is the most basic sandbox like template to start with.
I think it is an inherent difference between front end and back end developers. You guys don’t care what it looks like as long as the programming is constantly up to date and I don’t mind if I miss some updates as long as its designed well. You guys try to plan for every possible scenario and I design to make things as customized as possible. I have a million ideas of things I want to do designing a theme for a non-profit I work with, but I’m not always certain about writing the php to get the functionality on track so I post on here about it. Instead I get front end advice, suggesting I write an entire plugin for something that can be accomplished with a line or two of html and css, just to keep the plugin pure. Neither extreme is the answer, I’m just saying it is a bit lop sided right now.
We have to try to get things to work for 80% of our users; if we encouraged people to edit the default theme or any of the core BuddyPress files directly, most of those people are going to come back and complain when we release a new version of BuddyPress because they won’t understand what’s really happened.
Theme developers of course have two options — either as a child theme, of BuddyPress’ bp-default or one of the many other theme frameworks, or as a seperate/existing theme with the BuddyPress template files copied in. Both have their disadvantages and advantages.
@alanchrishughes I built mine as a child theme of Twentyten, not the bp default. 
@thekmen – let;s compare code & I’ll get it rolled in to the ticket. https://trac.buddypress.org/ticket/2382
@andrea_r You made a BP child theme to a theme that is not BP compatible?
@djpaul “if we encouraged people to edit the default theme or any of the core BuddyPress files directly, most of those people are going to come back and complain….”
That’s why I think it is important to start separating the BP plugin from themes.
