BuddyPress.org

I wonder though, how BuddyPress could handle the activity feed from an external blog. My guess is that it really couldn’t, unless you can set up some form of XMLRPC to the existing BuddyPress site, which to be honest I know absolutely nothing about right now to even think if it’s plausible.

I agree that it would be nice to link your one site to other BuddyPress sites, but I suspect that some site admin’s may want to moderate the content that is getting filtered through their domain. There would probably need to be some moderation involved. What do you do about the Buddy Bar at the top? Or does this link basically just kick them over to the external site?

In my opinion I almost think it would make sense, in the interim, to just use RSS to display the content from one blog on another, to fit it within the format of an existing site, at least until something like this comes to fruition.

http://www.mmaopinion.com

It’s the first release. Lots of changes coming up!

Awesome, will check it out today.

On an interesting side note, somewhere along the line I broke my connection from BuddyPress to bbPress again. Ha! I need to stop fidgeting with things soon I think.

/mu-plugins/bp-core/bp-core-adminbar.php but the css gets enqueued in bp-core-cssjs.php in the same dir.

There’s a bug in RC-1 that sends out the admin bar css after the site-wide.css so including your mods in there won’t do much good. Patch in : https://trac.buddypress.org/ticket/555

The wp_footer action ‘calls’ the admin bar.

Hi, I´m interested in making my own buddypress-home theme and buddypress-member theme, to fit my web site. I´ve been looking for information on the web, but I have not found anything good. Anyone has some kind of tutorial about it?

Alain

Hello everyone. Hi Burtadsit. I´ll try to explain using my poor English, I´m cuban. The error occurs in a Clean install, when you activate the home theme and try to visit the root blog, or the blog of any user previously created.

The page show the following error:

Warning: require_once(C:sitiossitiosocial/wp-content/member-themes/buddypress-home/index.php) [function.require-once]: failed to open stream: No such file or directory in C:sitiossitiosocialwp-includestheme.php on line 822

Fatal error: require_once() [function.require]: Failed opening required ‘C:sitiossitiosocial/wp-content/member-themes/buddypress-home/index.php’ (include_path=’.;C:xamppphppear’) in C:sitiossitiosocialwp-includestheme.php on line 822

How you can see, the application doesn´t found a buddypress-home directory inside member-themes. So, we solve this making a copy of the buddypress-member and renaming it to buddypress-home.

Changing the topic (I know this is out of forum). I´d like to make my own buddypress-home theme, and buddypress-member theme. Do you have any documentation about it???

Alain

Well, it could really go in a few different places. Let me take a look when I get to work to see where will work the best.

Here on BuddyPress, the “admin bar” has been nick named the “buddy bar.” It actually replaces the typical “admin bar” from a normal WPMU install.

The files for it can be found in the bp-core directory if you needed to modify it for any reason.

The buddy bar is actually loaded very last in the DOM, and it is absolutely positioned to top 0, so its essentially hovering over the body contents. Because there are at least two active themes at any given moment (home and member) you could either throw the css into homethemedir/css/site-wide.css, or all of the base.css for each theme.

But let me double check for certain.

This thread points to a domain mapping plugin for wp.

https://buddypress.org/forums/topic.php?id=1493

Any progress on this?

I’d like to install BuddyPress on a subdomain too (the top domain is a public website).

Would be an awesome feature!

I think this plugin would be very important because every community that grows will need multiple databases otherwise everything won’t get bigger..

I hope Nicola or Andy will do something in this way..

buddypress-member/css/base.css – line apx 495 – Make that be…

.main-column h1 a, #blog-info h1 a {

color: #646464;

margin: -120px 0 0 200px;

position: absolute;

}

buddypress-member/css/base.css – line apx 477 – remove

float: left;

bp-core/css/structure.css – line apx 110 – remove

float: left;

bp-core/css/structure.css – line apx 64 – remove

margin-left: 200px;

Give that a shot?

Hi John.

I have to test the xprofile stuff on the bbpress template tag level. I think I’m transferring data that could be serialized in $field_obj->data->value. Gotta check that.

This thing needs chat. You ever on IRC? A bunch of us hang out in irc.freenode.net #buddypress. I’m always there.

I like the inclusion of ‘signature’ in a profile field! Nice idea.

I’ve updated bbGroups to optionally transfer all users over to bbpress meta or just users who are in groups. Skipping the bbpress/buddypress utility user.

I’ve got all xprofile groups and group field values going to bbpress.

Got a template tag that allows getting any of those values by user, group, field.

Did some cleanup internationalization for text.

Now doing testing. Gotta look into the problem with tags for hidden groups showing up in the tag cloud. I don’t think you’d be interested in any of this. You’ve already got that stuff implemented.

I think that the only mod of yours I stepped on was the oci_get_user_filter() changes you included in there. I added another filter function oci_get_xprofile_filter($user) that adds all the xprofile fields to the $user array. It won’t break your mod, it’ll just add all the xprofile fields again.

/**

* oci_get_xprofile_filter()

*

* This filter adds all xprofile groups and group fields to bbpress

*

* @param <array> $user

* @return <array> $user array for xmlrpc transport

*/

function oci_get_xprofile_filter($user){

$xprofile_groups = BP_XProfile_Group:: get_all(true); // all except empty groups

foreach($xprofile_groups as $group){

foreach($group->fields as $field){ // all fields for group

$field_obj = new BP_XProfile_Field($field->id, $user,true); // this field

// xprofile_groupname_fieldname to prevent conflicts

$user = array(‘group’ => $group->name, ‘name’ => $field_obj->name, ‘value’ => $field_obj->data->value, ‘type’ => $field_obj->type);

}

}

return $user;

}

add_filter(‘oci_get_user’,’oci_get_xprofile_filter’,10,1);