There was a free plugin but it has not been updated for some time https://wordpress.org/extend/plugins/import-from-ning/ There have been many changes to BP since the plugin was released though.
There’s a premium plugin http://premium.wpmudev.org/project/ning-to-buddypress-user-importer/
which states it’s compatible with latest version. There’s a link to contact them on same page for any pre-sales questions.
@cleaus I just found out that DailyPost is hosted in WP Theme Repo and the content-page.php code has the “missing” lines, see https://themes.svn.wordpress.org/dailypost/1.0.5/content-page.php
I see that the theme has a PRO version as well.
So are you using the pro version or the free one from WP theme repo? If you’re using the one from the repo, you should download another copy of the theme and re-upload it manually via FTP to make sure all files are there and I will work from the code in repository. If it’s the pro version, it’s weird that it’s missing some lines which are available in the free version.
BP 1.6 says this: Improves security of registration process, by relying on WordPress validation functions (#3949)
Does this mean that WordPress moderation plugins will work with BP now?
Paul, anyway it’s pretty simple to use both methods. We know that default wp_users support first_name, last_name, nickname and description (bio). Maybe you could make possibile to modify each of that from buddypress (i made it in my theme) and make a base group with these fields. Then if administrators want to add more fields and groups you could populate xprofile table. In this way you could have a more deep integration into WordPress.
OK, I’ve just tested BP 1.6.1 on WP 3.4.2 (BP Default theme) in my dev site.
Yes, the same issue is still persistent!
Also, I found an interesting post and I wonder if AJAX change is related with this issue…
AJAX changes in BuddyPress 1.6
Cool 
so a more deep integration into the wordpress core… Speaking of This, i’m just wondering why buddypress doesn’t use user_metadata and have a proprietary xprofile table.
Just to add @mercime I am a real novice to WordPress and BuddyPress so sorry if i dont completely understand!!
@fitnessblogger if you have child theme of bp-default theme or are using the BP template pack plugin and moved BP template folders/files, then copy over this file https://buddypress.trac.wordpress.org/browser/tags/1.6.1/bp-themes/bp-default/blogs/create.php following the directory structure and make the change.
@dcavins Hey did you get a solution? I have exactly the same problem on a Linux server (RedHat).
Latest wordpress and buddypress versions, default theme… Looked all over the internet…
@abovenbelow,
give this a shot… I’m about to: https://wordpress.org/extend/plugins/buddypress-groups-extras/
You may also want to check out: http://buddydev.com/tag/bp-gallery/ for the Gallery (but Brajesh is working on the next version), BP Media’s BP Album+ could also work for you; and you could give Boris’ Mapology plugin at http://shabushabu.eu a shot as well.
Try to bump this topic too , Buddypress is much more in advance from those last posts so maybe new BP versions will allow it, is anybody here who use @justin_k Justin’s WP-FB autoconnect and who has the same problem as @ifanatics in the first post above ? I succesfully use premium WP-FB autoconnect too and have the same problem as him, users who register to my website via this plugin can see every page even when I have restricted that page to only one different role (I have created 2 new roles , “club” and “job_applicant”, both new roles works perfect when I want to show and hide the content to specific user but only facebook users can see everything 
, (they can see everything even if I manualy assign them a different role in user profile edit page.
Other problem is what can I do to show facebook users in EDIT author drop down field in EDIT post page ? I can see there only wordpress – buddypress users , but not Facebook users despite of they are all everywhere even in members directory, from that reason I cannot assign them any blog post / CPT post
@Roger Coathup – sorry didn’t realized that I should have posted seperately, will do and ash other questions on the wordpress forums, thanks
You should ask these as separate questions – the first two issues are general WordPress (not BuddyPress), so best asked on the wordpress.org forums.
Post issue 3 as sep question on here, and issue 4 you could ask to @pollyplummer on her group for the plugin
Two plugins which look current and could help you https://wordpress.org/extend/plugins/activate-users-in-buddypress/ and https://wordpress.org/extend/plugins/wp-approve-user/
As usual, the following disclaimer applies: backup DB and files before activating plugin
You could try editing /profile/edit.php in your theme to use wp_editor() instead of textareas.
Have a Google for guidance on using wp_editor() – it’s the WordPress wrapper around tinymce.
You’ll probably also need to change the filters that sanitise your text inputs to ensure they allow the tags that you want to support in your editors.
Based on the HTML structure of your theme, you need to change 16 template files within the 6 BP folders transferred to your paradise theme folder in server during the compatibility process.
I’m trying to do the exact same thing right now. It has gone smoothly, bar version 1.5 featuring no CSS for the admin bar, then on upgrading to 1.6 the admin bar CSS was fixed, but all the menu items in the admin bar disappeared.
Any ideas on how to get the BuddyPress bar menu items back?
I chose to use the new admin bar menu instead of the older one, so perhaps I could go back to that to fix it? It seems like moving to the regular WordPress one would be best though.
Well… mixed results. Replacing the 1.2.8 files with those from 1.5.6 blanked everything, including wp-admin. I tried putting them both in the plugins directory, de-activated 1.2.8, then tried to activate 1.5.6 but it wouldn’t activate.
So essentially the upgrade so far has been a failure. On the other hand it is, as I mentioned, a temporary measure so that isn’t a catastrophe. In the process, though, I discovered that the files we’d been sent originally had been on a mac at some point, and the file system was littered [sic] with mac resource forks. I used ‘find’ to delete those, and we seem to be in a much, much better state than previously! Apparently WordPress tries to load and execute the resource forks where they’re present.
There are still egregious problems with the site, but I’m inclined to think that most of them are to do with the corruption in the db data we were given initially, e.g. existing comments seem to have become disassociated from their original posts, whereas new comments are working properly.
Thanks very much, everyone, for your help. I’m not marking this as resolved since my original problem hasn’t been solved, but I think we’re probably going to leave BuddyPress alone for the moment. WordPress is great when it works, but I’ve found it pretty opaque to debug; thanks again for helping me out!
Cheers,
Ben
“They said they were
hoping to show off “that
wow factor, “WordPress Opensource Wonder”
this is not spam. This is rather an encrypted message. Buddypress is still stuck in 1,********s. No major release recently. Its 2.0 phobia
“The audience liked
their number, which ended
with all of the guys dancing in trays of water”
“Sharon liked it. Howie liked it but said it was “one-dimensional.”
“Howard thought they “did well,” but also said it was “deja vu” – we had seen it all before or we were mesmerized”
@newbie2011 we have a list of “template-packed” WordPress themes @ https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/#template-packed-wordpress-themes
If you need assistance for your current theme, open up your theme’s header.php, copy all code, paste in pastebin.com, click submit and post the generated URI here. Do the same for your theme’s index.php, page.php, sidebar.php and footer.php
Thanks everyone! I don’t have a convenient test environment available, but I have backed up the entire database and all the files, so I think I’ll cross my fingers and try stwc’s method, as the easiest – assuming it works!
If it doesn’t then I’ll revert and we’ll try a different approach. Ultimately we’re planning to move all the functionality off the WordPress installation and onto our own system anyway, so there’s a limit to the amount of time I want to put into making it work properly.
Thanks again everyone, I’ll report back!
problem solved!
I’ve installed Display Widgets https://wordpress.org/extend/plugins/display-widgets/
Everything works perfectly now.
@r-a-y Thanks again!
Agreed with Roger.
You would have to do two things:
* modify the registration template (/registration/register.php) to remove the username field.
* modify the registration validation routine to use the first and last name as the username. If you’re already familiar with WordPress development, the appropriate function to look at is bp_core_validate_user_signup().
