Hey, i was using a customised theme, however i just tried it with the default theme and the same thing occurs there… i’m running WPWU 2.7.1 and the latest BP version that you just released. I’ve just tested this out on the previous version i was testing with WPWU 2.7 and BP RC1 and the same thing occured there. I’m now wondering if it is perhaps a permission issue? How does Buddy Press work with the group avatar? The profile avatars are working fine. Is there a folder somewhere which is created saving the adjusted images?? maybe the permissions arn’t writable?
In your member theme in /wire/post-list.php change this:
<?php if ( bp_has_wire_posts( bp_wire_item_id(), bp_wire_can_post() ) : ?>
to this:
<?php if ( bp_has_wire_posts( 'item_id=' . bp_wire_item_id() . '&can_post=' . bp_wire_can_post() ) ) : ?>
Well, it’s obviously down to each individual theme. In the nicest way possible, I doubt you are going to get anyone here going in to tell you what HTML changes you need to make to each theme to get it to work the way you want. Suggest talking to each theme’s author.
Are you using the latest default themes? What version WPMU/BuddyPress?
Hi
What versions of WPMU and BP are you using? How did you install them – upgrade or fresh install? And are you using a custom theme – if you are, does it work if you revert to the standard BP theme (to test)?
Thanks a lot for the information 
might work for you, it hasnt for mine but others seems to have made it work.
make sure to check the theme part of the rc-1 to rc-2 upgrade installation.
Don’t mind at all and thanks for the very helpful info!
– Steve
Bpfan,
You can install the same old standard WordPress theme if you’d like, but keep in mind that it won\’t have any functions that tap into BuddyPress at all. Yes they will work, exactly like they did before.
You upload and install them in the same place you’re used to, wp-content/themes/
Then they must be activated in the Site Admin->Themes area.
(Hope you don’t mind, I renamed your topic title so it doesn’t confuse “Member Themes” with “Themes for Members” haha!)
Check the new sticky regarding the theme preview.
I’m going to integrate bbPress on my test install and give it a go myself this evening.
Andy reviewed and made some additional updates to v1.2 of the Skeleton Component. It is now official and is located here:
http://testbp.org/resources/bp-skeleton-component-1.2.zip
yeah mee too.. i have transfered the profile/index.php accross to my theme.. but its still not working.. 
i think he’s referring to this:
https://codex.buddypress.org/getting-started/installing-buddypress/upgrading-from-rc-1/
which i followed but still not showing me my wire unless in default buddypress theme..
A new version of the Skeleton Component for plugin developers is is now available. Please see this thread for details: https://buddypress.org/forums/topic.php?id=2329
Ok, I surrender. I was wrong. Yes, changing the groups slug does trash the icons. I’m thinking to myself “These people are nuts. I just changed the BP_MEMBERS_SLUG to ‘boysinthehood’ and nothing changed”. I picked the only slug that doesn’t have a dependency in the member theme css for an icon.
The member theme\’s userbar does bp_get_nav() which generates the html for the user nav bar. The individual nav items \’css_id\’ is the slug for each component. You change the slug you change the \’css_id\’ in the nav menu.
This isn\’t a bug really. Its a side effect of having the flexibility to actually change the slug. The component slug is the only site wide identifier for a component.
I don\’t see any easy way around this. The css defaults to what the component default slug is. Which is \’groups\’. Changing the slug invalidates the css.
Ok, I solved this.
When changing slugs, css needs to be hacked a little to show the icons properly. For example, when you change groups slug to communities in bp-custom like this:
define('BP_GROUPS_SLUG', 'communities');
You will need to find the following css entry from base.css locating at bp-themes/buddypress-member/css/.
li a#user-groups, li a#my-groups {background: url(../images/groups_bullet.gif) 88% 52% no-repeat;}
Copy above, create a file called custom.css if you haven’t done yet. Modify the css to:
li a#user-communities, li a#my-communities {background: url(../../images/groups_bullet.gif) 88% 52% no-repeat;}
And upload custom.css to bp-themes/buddypress-member/css/custom-components/
That’s it!!
@Erichamby-
I hope that TMD works well for you!
Incidentally, I noticed that their BuddyPress tutorial is out of date. They have not been keeping up with the changes in theme directories. Also, they state that:
As an addon to the official WordPress MU, BuddyPress is fully compatible with all the plugins and themes of WordPress and does not limit its functionality in any way
This is not true. There are several incorrect statements there. For instance, there are a number of steps that must be taken if you are using a custom WordPress theme with BuddyPress. I hope they’re good at tech support!
Actually, no, the issue is there with the default bp-member theme as well. I’ve tried it with both the default and my own customization of the same. For whatever reason, all of the entries in my profile fields are hotlinked.
See: http://blogpei.com/members/admin/
Thx
@natscrim: Check out “download zip” instead of clicking on the link ; because the link is pointing to the RC1 version while the “download zip” link is pointing to the right link.
yeah, it’s bug https://trac.buddypress.org/ticket/691 if anyone has anything to contribute
Thanks, Nicola,
Yes, I removed the plugin and upgraded to 2.7.1 — but… after I reinstalled RC-2 for second time and got the blank preview, I didn’t go further, assuming it would be the same as before. I just tried it, and it works!
Thanks, again.
Nat
have you removed bp plugin in mu-plugins and updated to wpmu 2.7.1 ?
Natscrim – the preview thing is a known issue. I have spent about three hours investigating it with jjj and not getting anywhere. I have made a ticket on trac.
But, for me, even though the preview was blank, the theme worked on the homepage.
So the problem is in your custom theme then? It’s a tricky nuggest but read through https://buddypress.org/forums/topic.php?id=2298.
