that someone was me – https://buddypress.org/forums/topic.php?id=2893 what I had noted is that sam’s plugins is essentially the same as bp-forums-bbpress-live.php and the only answer (at this point) is to manually construct the bp_forums_get_forum() as you’ve suggested. the problem I was incurring previously was avoiding having to use the forum ID as an argument – when set to null it returns the most recent topics. https://trac.buddypress.org/ticket/375
No, i just looking for partner
I sometimes think we shouldn’t bundle the Skeleton theme with the BuddyPress .zip. It confuses some people.
If you are not in a hurry then I would recommend waiting for awhile. At some point, BuddyPress will be configured to function on single-user WordPress. I do not have a timeline for this as it has to do with merger of the WPMU codebase into WP.
3125432Inactive
Just an update. Have played around with this a bit and sometimes the sitadmin dashboard Users section that allows you to select the preferred name to be displayed publicly works and sometimes it doesn’t.
I’m thinking that this may have something to do with the Buddypress General Settings: Disable Buddypress from WordPress syncing? This is a total mystery to me what that means or is supposed to do. Anyone?
Anyway, the fix that seems to work is a MySql query that anchors from the user id # and then you could structure it to replace the current data in the value field of the wp_bp_xprofile_data table with the data from the user_login field of the wp_users table.
I have no idea how to do create that query but I am sure it is pretty easy.
– Brian
roseeveltrp, you’re correct!
You need WordPress MU.
BuddyPress only works with MU at this moment in time.
Some day down the road BuddyPress will support regular WordPress, but not now.
Here’s a good guide for transitioning from WordPress standard to MU:
http://welcome.totheinter.net/2008/10/04/how-to-migrate-from-wordpress-to-wordpress-mu/
It helped me!
what version of jQuery we can expect to see in the next BuddyPress update?
Well, based on the new features of WP 2.8, which WPMU will merge into its codebase, I’m going to guess jQuery 1.3.2. Perhaps Andy has a different idea.
Just to add I have had a smilar no cropping issue (leaving black thumbs) and isolated the issue down to the WP Carousel plugin which iteslf resolved a previous issue I was having with an old jQuery image gallery!
I am now stuck between a rock and a hard place- have the nice image gallery rotating on the home page OR have the cropping fucntions working correctly wihtin BuddyPress 
Weirdest issue with this jquery compatabilty theory is that I actually modified the WP Carousel plugin so it didn’t pull in it’s own jquery.js file so there SHOULD be no conflicts.
Will get in touch with the plugin authors but can I ask Jeff or anyone else what version of jQuery we can expect to see in the next BuddyPress update?
If I know this I can at least give the plugin developers a little more idea as to what I would like in an ideal world (after 1.2.6) but I can see some late nights getting friendly with jQuery ahead zzzz
I spoke to apeatling about this on IRC a week or two ago, and he said it was something he was aware of. You could make a ticket on the Trac just in case it is forgotten – use the same username and password for there as you do here.
I have to do something similar. Not looking forward to it…
I’ve found this plugin:
User Import for BuddyPress (All Fields)
To export member data from another WordPress installation you could use this:
Users to CSV WordPress plugin
Haven’t gotten to testing this yet, so let me know if it works…
You do not need to start another thread about this – you’ve posted in one other. I’m going to close this thread so we keep the discussion in one place.
Hi slavd
Thanks for the post. This bug was fixed in the SVN trunk a while ago, so I’m going to mark this post as resolved. Thank you very much for taking the time to post here!
3215850Inactive
+1
I’ve been running a ning network and wordpress blog in parallel. Slightly integrated by way off rss feeds, but nowhere near enough. Likely to jump onto buddypress at some point.
I can confirm this problem – I created a ticket here: https://trac.buddypress.org/ticket/799 – It looks like the unlink code don’t check wether the Images are Identical.
3125432Inactive
Jeff,
Thank you for taking the time to try and help us! This may seem off topic but every person on this board should take a moment to say “Thank You!” to Burt and Jeff and Andy, and the countless others who work to help solve problems.
This is a shout out to each and all; could you check your db’s using phpadmin or whatever you use to examine your wordpress/buddypress database and tell me what ‘user_status’ setting you see for the admin, typically ID#1?
Thanks,
Brian
Burt & Mike –
Thanks for the prompt reply. Tried upgrading both manually and with the built-in plugin install function. Also tried clearing out the BP tables from the database (the site has not launched yet) hoping that would kick things into shape.
2.7.1 was the first and only version of WPMU installed, upgraded BP from 1.0 to 1.0.1 and that’s when the themes died. Also, no hyphens in the themes’ directories.
Went through the code and was able to see what you were talking about in terms of setting the theme_root variable to /bp-themes/, but any idea why it would be doing so outside of member pages?
If the plugin is active, if I go to /wpmu-themes.php or /wpmu-blogs.php? in the WPMU backend, to activate themes all I see are the BP themes. Correct me if I’m wrong, but before it would also show me themes in the /themes/ directory as well. Is this an intended function? I’d prefer not to move my non BP themes into the bp-themes/ as disabling BP would then kill the site.
Any help you could provide would be greatly appreciated.
– Ben
(ben at gwstudentassociation dot com)
If you are offering paid work, you should post your request here: https://buddypress.org/groups/buddypress-job-board
Hey, no reason to say sorry!
There are too many variables of which to keep track. It is sometimes necessary to bounce issues off of others.
Hi, thanks for the nice support. Yes I know it is for developing. I was wondering, thinking a example should work. But it was my stupidity. There was an old bp-dev plugin example in my plugin folder I think that curse the problem.
Thanks and Sorry
If it’s not showing on all your blogs then check the setting of: wpmu back end > BuddyPress > General Settings > Hide admin bar for logged out users?
If some themes are still not showing the admin bar then that means they are not written to calll wp_footer() in the theme itself.
this post might help you answer some of your questions… https://buddypress.org/forums/topic.php?id=3204
Anything new since two months ago? There have been many changes to BuddyPress over that time!
Have you searched the forum and read this thread
If so, then you need to provide more of an explanation than “Having the same problems with avatars”. That tells us exactly nothing to begin the process of providing support. Please see this thread as well.
I will say that I have elected to delete some lines of code to remove some functions in the core files but they aren’t super critical, in my opinion.
Okay, as I’m sure you know, this type of sentence scares all of us who try to offer support. 
The real question is this:
If you boil everything down to the lowest, common denominator (LCD), does everything work. This means using BuddyPress without any core mods, using the default themes, and not running any other plugins in WPMU except BuddyPress.
If everything works, then this is an issue caused by something you are doing. If you still have this problem, then you need to talk with your hosting firm or system admin (if you are in a business/institutional setting) because it could have something to do with your server setup (DB server maybe).
But, if everything works as it should when you’ve distilled the WPMU/BuddyPress install down to the LCD, then it clearly is something you’re doing. It could be your core hacking, the single-sign-on coding, a 3rd-party plugin conflict, any combination of changes. You need to go back to the bare bones foundation and then start adding stuff back, implementing your changes one at a time and throughly test in between each new change.
The inner workings of the e-mail spam detectors are strange and mysterious. You are probably right in that having your mail sent by a server on a domain hostname different than the domain specified in the “from” field in the mail (your domain) counts against them. I’d set up a big “check your junk mail” blurb as suggested above, and recommend your members to mark all BuddyPress e-mails as “not spam”.
