BuddyPress.org

Quick suggestion, although I bet many people won’t run into this issue…

function oci_get_userdata($u){

$u = (int) $u;

$user = bb_get_user($u);

if ($user->bbGroups) {

return stripslashes_deep((array)$user->bbGroups);

} else {

return stripslashes_deep((array)$user);

}

}

Then, I changed…

function oci_user_name($u){

$bp_user = oci_get_userdata($u);

if ($bp_user['fullname']) {

return $bp_user['fullname'];

} else {

return $bp_user['display_name'];

}

}

Basically, I integrated my forums before installing BuddyPress, so there are users that haven’t updated their BuddyPress profiles that won’t have fullname’s yet… This way I have all of their normal info to manipulate later and still get their original wordpress display_name to fallback on…

There is probably a much prettier way of doing this, but this is the solution my tired brain could come up with for now.

I had a heck of a time converting my WordPress.org install DB over to WordPress MU, simply because my WP export/import only worked for about 10% of the data.

I currently have a setup like you’re looking for, from delsolownersclub.com and delsolownersclub.com/blog. I think I did this my chance, because I made a few mistakes in my transition myself.

So, yes it’s possible, and it actually shouldn’t be too difficult if you already have WPMU installed on your /blog directory. If you simply have WP.org there, then it’s a little bit of trial and error and DB dumping and editing.

The other thing I ran into as an issue were the attachments and their directories, and the associations for those files in the database. Example, WP.org saves files in the root/uploads directory, but WPMU saves them in root/wp-content/blogs.dir. That meant dumping the whole database to a .txt file, searching and replacing /uploads with /wp-content/blogs.dir, and then importing the whole thing in phpMyAdmin.

I did it that way for myself rather than running any weird SQL queries because my site could afford the downtime and because I didn’t want to miss anything, causing bad image links, etc…

Does that make sense?

export your blog to the wordpress format then install mu and buddypress, your blog can then still be accessed by /blog, but obviously you will have to import it first,

most of the plugins will work with mu but some will not, i guess you can only hope and try them out

you will need to add your plugins again, i suggest you add them one by one to see what is working and what isnt, hope that helps, let me know if you need more help

There’s a few WP plugs that might work (I’ve not tried them and cannot guarantee they will work):

https://wordpress.org/extend/plugins/login-style/

https://wordpress.org/extend/plugins/bm-custom-login/

etc.

You should use wordpress hooks to do that,

but if it works that’s ok, but when will be the next update you’ve to hack the code again

OT “haaah “Che culo!””

You can also check out the following plugin as well

https://wordpress.org/extend/plugins/peters-login-redirect/

Trent

I think the idea is not to have BuddyPress permanently alter the WordPress related data.

I’m new to BP and so I’m not familiar with how all the functions work, but what in the original WP data structure would be altered by deprecating fullname in favor of using the WP fields?

…then really BuddyPress should be able to modify ALL of the original WordPress user info exactly like the profile admin panel does…

I would like that, actually. Or at least to have the option to have the profile be able to modify that information.

I want the original WP functionality that allows a user to choose which fields — username, first name, last name, or nickname — to display for them. I thought that was a great addition to WP and I don’t like that installing BP has effectively cut me and my users off from that choice without some serious code modification on my end.

I think the idea is not to have BuddyPress permanently alter the WordPress related data. Right now, and please correct me if I’m wrong, but past of the design and development process of BuddyPress is that it can be added and removed without any changes done to the WPMU data structure, apart from conveniences like changing a password, etc…

You can rename the “Full Name” in the BuddyPress to say “Nick Name” or “Display Name” or whatever you’d like, and then code your themes to use that info if you so choose…

To be honest, from a developers standpoint, I like how it is right now, as it allows me to keep things separate. If you’d like to open up the ability to modify the fullname, then really BuddyPress should be able to modify ALL of the original WordPress user info exactly like the profile admin panel does, with website, info, firstname, lastname, etc…

I’m with DJPaul; I would like to see BP’s proprietary fullname field deprecated and have WP’s native fields be used instead.

Not only would it allow for more customizability/adaptability of BP themes, plugins, etc but it would also get rid of an extra field that, as far as I can tell anyway, can be handled just as well with WP’s first_name and last_name fields.

I agree that we should put this suggestion into a trac ticket.

@jimthedj65, Regarding WP video framework plugin integrated into BP, you need to liaison with ddmitry on this. He got it working on his site !!

https://mu.wordpress.org/forums/topic.php?id=10778&page=2

When you use deep integration bbpress clears all the actions and filters. bp runs on actions. It does this as part of the load sequence.

In bb-settings.php:

/**

* Remove filters and action that have been set by an included WordPress install

*/

if ( defined( 'ABSPATH' ) ) {

$wp_filter = array();

$wp_actions = array();

$merged_filters = array();

$wp_current_filter = array();

}

When I’m using xmlrpc I have to manually fire up the bp globals I want to refer to like:

function oci_bp_group_forums() {



// only do this if the xmlrpc server is firing up and we are servicing a request

if ( defined('XMLRPC_REQUEST') && XMLRPC_REQUEST ){

// bp's globals don't get set until a 'wp' action occurs. this seems to be all that is needed.

bp_core_setup_globals();

groups_setup_globals();

bp_activity_setup_globals();

}

}

add_action('init','oci_bp_group_forums');

That gets triggered by the end of the wp-load.php sequence. do_action(‘init’) is the last thing that happens there.

bp gets woke up by listening to the ‘wp’ action. I think all of bp gets activated by ‘wp’.

I just remember having some problems with xmlrpc and the ‘wp’ action so I manually tied things to the ‘init’ action. All the plugins for bp load, it’s lots of other stuff that gets initialized by ‘wp’.

You MUST share the database for them to be able to share users. bbpress will create some tables in your wordpress mu database and share the users table. If you keep separate databases, deep integration will never work.

It actually doesn’t matter if you do it during installation or after… it turns out to be the same.

Have you seen this article:

http://bavatuesdays.com/integrating-wpmu-buddypress-and-bbpress/

It was extremely helpful with my setup and includes the video you mentioned, with some additional pointers. Also read the comment section for some addtional info.

Just make sure you have the latest versions of both and start off fresh. Follow the article I quoted and give that sigh of relief when you switch from WordPress MU to bbpress and see “Welcome admin!” on top instead of “Login”….

My admin_bar at admin wordpress mu dashboard doesn’t translated, only de admin bar at buddypress area is translated.

./wordpress-mu-root-dirctory/whatever-you-want

Mine is at delsolownersclub.com/discussions/

You just need to make sure you reference that directory everyplace you need to within BuddyPress and bbPress to make sure they see each other.

SWEEET SUCCESSSSS!

Okay… For those of that might be using “deep integration” namely using your BuddyPress/MU functions in bbPress, at the time of this writing at the top of your bb-config.php file, put…

if ( !defined( 'ABSPATH' ) & !defined('XMLRPC_REQUEST')) {

include_once( 'absolute/path/to/your/wordpressmu-directory/wp-blog-header.php' );

}

This way, it only tries to include the MU/BP functions if they haven’t already been defined and if it’s NOT a xmlrpc request!

DUH! Yay! Burt, haha you rule…

I am attempting to install the forum myself now. Ok so what I did first was to go ahead and in the root dirctory created a folder called forums. Next, what I did was to go ahead and download from wordpress the bp press forum module. Is this correct so far?

Regards,

Charles Pisano

Question about step 1.

You say that the user has to be created on the “bbPress” side. Does this refer to a user that is registered through register.php via the forums? What if my forums were integrated from day 1 with WordPress? Is it okay to just use the “admin” keymaster account?

Question about permalinks and .htaccess.

I am using pretty permalinks on the bbPress side, and there is an .htaccess file on the root of the bbpress install folder. What would I want to look out for to prevent this from causing a problem?

Question about “deep integration”

I am currently including my wp-blog-header.php file inside my bb-config.php file. Will this cause conflicts?

Question about what to do if I swear I’ve followed the steps the way they are written and the ways everyone else has said, and it isn’t working.

ok I guess I spoke too soon. Had this in red with 4040 not found after it:

http://twitterfic.com/wp-content/mu-plugins/bp-core/bp-core-ajax-handler.php

then the other code:

Date

Thu, 19 Feb 2009 04:16:47 GMT

Server

Apache

Cache-Control

no-store, no-cache, must-revalidate, post-check=0, pre-check=0

Expires

Thu, 19 Nov 1981 08:52:00 GMT

Pragma

no-cache

X-Pingback

http://twitterfic.com/xmlrpc.php

Last-Modified

Thu, 19 Feb 2009 04:16:47 GMT

Keep-Alive

timeout=15, max=99

Connection

Keep-Alive

Transfer-Encoding

chunked

Content-Type

text/html; charset=UTF-8

Request Headers

Host

twitterfic.com

User-Agent

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5

Accept

*/*

Accept-Language

en-us,en;q=0.5

Accept-Encoding

gzip,deflate

Accept-Charset

ISO-8859-1,utf-8;q=0.7,*;q=0.7

Keep-Alive

300

Connection

keep-alive

Content-Type

application/x-www-form-urlencoded; charset=UTF-8

X-Requested-With

XMLHttpRequest

Referer

http://twitterfic.com/members

Content-Length

888

Cookie

wp-settings-time-1=1234978735; wp-settings-1=m0%3Do%26m1%3Dc%26m2%3Dc%26m3%3Dc%26m4%3Dc%26m5%3Do%26m6

%3Dc%26m7%3Do%26m8%3Dc%26m9%3Dc%26m10%3Dc%26m11%3Dc; wp-settings-time-2=1234896835; __utma=253961357

.2322033939621672000.1234866299.1235007210.1235014438.11; __utmz=253961357.1234900041.3.2.utmcsr=trueblood

.twitterfic.com|utmccn=(referral)|utmcmd=referral|utmcct=/groups; wp-settings-2=m0%3Dc%26m1%3Dc; wp-settings-time-5

=1234989991; __utmb=253961357.60.10.1235014438; PHPSESSID=4bv8ld7abk3iutqqhht3jo9d06; __utmc=253961357

; wordpress_test_cookie=WP+Cookie+check; wordpress_logged_in_=kitchenbitch%7C1235188924%7C7aa68ef091

4f0885b507970bff70071e

_wpnonce

f149be8ca2

action

addremove_friend

cookie

wp-settings-time-1%3D1234978735%3B%20wp-settings-1%3Dm0%253Do%2526m1%253Dc%2526m2%253Dc%2526m3%253Dc

%2526m4%253Dc%2526m5%253Do%2526m6%253Dc%2526m7%253Do%2526m8%253Dc%2526m9%253Dc%2526m10%253Dc%2526m11

%253Dc%3B%20wp-settings-time-2%3D1234896835%3B%20__utma%3D253961357.2322033939621672000.1234866299.1235007210

.1235014438.11%3B%20__utmz%3D253961357.1234900041.3.2.utmcsr%3Dtrueblood.twitterfic.com%7Cutmccn%3D(referral

)%7Cutmcmd%3Dreferral%7Cutmcct%3D%2Fgroups%3B%20wp-settings-2%3Dm0%253Dc%2526m1%253Dc%3B%20wp-settings-time-5

%3D1234989991%3B%20__utmb%3D253961357.60.10.1235014438%3B%20PHPSESSID%3D4bv8ld7abk3iutqqhht3jo9d06%3B

%20__utmc%3D253961357%3B%20wordpress_test_cookie%3DWP%2BCookie%2Bcheck

fid

5

I think this makes perfect sense, but I think the word “tag” needs to be used carefully, because WordPress has sort of defined the use of “tags and a “tag cloud” as a specific function, and this does not sound like that.

This just sounds like a collective list of links that the group can add things to, more like relative content than tags in my mind. Similar to the “blog this” part of WordPress that lets you be on any web page and via a bookmark, create a blog about it, this would allow members of a group to be on either 1.) a page/post/attachment within your site, or 2.) any site on the web, and add it as a relative link for your specific group.

Am I making sense, or going off in the wrong direction maybe?

as i said, i made that same think you’v planned to do

not using wires but integrating buddypress membertheme with wordpress loops