BuddyPress.org

Mine is doing something similar, I think.

WPMU was installed first… worked fine, tested some blogs and users.

Installed BP via the Plugins installer… activated it sitewide, no errors.

Moved (not copied) the bp-themes folder …

Put BP Home theme into themes directory & activated it for the home blog.

Results: none of the links in the My Account dropdown work — all point to

http://blogsite.ca/members/blogname/…

… when our WPMU is set up to have the blog name at the beginning, like:

http://blogname.blogsite.ca

Modifying the My Account addresses (manually, for testing) to this doesn’t work, either:

http://blogname.blogsite.ca/members/blogname/… OR

http://blogname.blogsite.ca/members/…

That, and the homepage for our site no longer shows a blog page, but a login page — and it doesn’t accept my login & password combo (which worked just fine to get into the Dashboard for my blog).

This question is about wpmu and not buddypress. anyway, those nonactivated users are deleted after 3 days (as far as I remember). There’re also plugins to enable the same email address registrations.

Hello Andrea_r

I just installed BuddyPress v 1.0 2 days ago to a new WordPress MU install. Got it running fine except for the member blog theme thing where members have the default WordPress MU theme. I followed your instructions above and copied the bphome theme, changed the theme name, changed the style.css file header name from home to blogs and deleated the home.php file. I moved this new theme to /wp-content/themes folder and activated the theme. But when I go to a members dashboard and click on the theme to activate it, it comes up blank in the preview window.

Any ideas what went wrong?

Thanks Mark

http://photomark.ca/boozoo

Actually, I just did this on a test bed. Took maybe ten minutes.

make a copy of the home theme and move it somewhere.

rename the folder to something obvious, like bp-blog-theme.

Edit style.css and change the theme name to be Blogs instead of Home.

Delete home.php.

move the new theme back into wp-content/themes/. Activate it under Site Admin -> Themes. Go to a member blog (you have a test blog, right?), under Appearance and activate the new BLOG theme.

Give it a whirl and let me know how you make out. There’s other regular WPMU plugins to enable the theme by default on a new blog. My fave: http://wpmudev.org/project/wpmu-blog-defaults. That way the blog creation part is seamless and looks well-integrated.

copy this, add to it, paste it below in your post…. this will get a little overboard i’m sure, but we should list as much as we can and then narrow it down based on:

– if it’s possible

– time to complete

– cost

Features Request:

browser=person browsing the website

user= the individual user/profile owner

– seamless integration with buddypress

– this becomes a component that is activated through the bp admin menu

– and general settings are controlled by the admin in the wp-admin subnav

– not a plugin/mu-plugin

– user can select to only show pics/vids if your the users friend, or show anyone

– user can subscribe to pics/vids gallery rss just like activity rss

– browser can select “view random gallery” or “view random video” from the bp nav bar

– user has “gallery options” under their profile menu

– add/upload/remove/rename/add caption to images and videos

– user has “gallery settings” under their settings menu

– make pics/videos public, show to friends only, etc

– all media uploaded is searchable through the /members page

– a new <directory> is created called “Media” just like the “groups” or “members” or “events”

– this directory shares the default theme of BP and yet is customizable because it has it’s own directory/index.php and directory/media-loop.php (just like BP)

– admin decides how media should be stored

– on the website server

– or on kultura (i have no need for this)

– etc

– admin decides max file size, max storage amount per user and is able to delete any media uploaded

– user is able to choose which uploaded image is set as their avatar

– user is able to create galleries and select a default gallery icon/image (myspace)

– galleries could contain both video and images and are browsable as thumbs

– thumbnail image is “thickbox ready” and pops up both pics and video into a jquery thickbox with button for next / previous / close etc

– Gallery content/information/descriptions etc becomes bp-Xprofile data that can gotten and displayed much the same as regular bp-xprofile data (get_bp_xprofile data ect)

– except for the admin options, all gallery controls and content remain on the front-end/profile only

the list goes on and on… and there’s many ways this could all be done

add to the above, remove stuff (say why you removed)

I dont think these features are “too much” considering there’s $700 available for this project… I’m also open to a different developer…. this should be someone who lives and breathes buddypress and who keeps current with both wpmu and bp trunk versions

we would also need to know/specify which install we want this created for

wpmu 2.7.1 + BP RC1

wpmu 2.7 + BP RC1

wpmu 2.7.1 + BP latest trunk

etc… because chances of this working well on all the different install variation is tricky

worst case scenario, all we get is the $200 job and we have to make due

(im still down with that too)

I would like the developer to brainstorm and come up with a list of features that THEY think are possible considering the budget

$200 gets you ___________.

$700 gets you ___________.

($700 would get us something pretty damn cool from the right dev… and remember, if it’s done right Andy will add this to the BP core which I believe is the best option)

bp stores information related to the blog you deleted and also for the user. To get rid of all the info that the user has generated you have to delete the user in wpmu Site Admin > Users. Deleting the user will remove from bp:

* all profile data for the user

* all recent blog post records for the user

* all blog post comments for the user

* all sitewide activity items for the user

* it flushes the cache

* all group memberships for the user

* all friendships for the user

You can grant additional users the site admin role in Site Admin > Options > Site Admins

List the user login names you\\\’d like to have that role. Site admins are the only users that can go on any blog and delete a post. Deleting a post from a blog removes the recent blog post record and the activity for that post.

Here are the instructions from Burt to test your host/server setup for XML-RPC support.

Follow this link to download the XML-RPC test that Burt created: http://ourcommoninterest.org/downloads/xmlrpc-sayhello.zip

The test consists of two files. The first file is a bbPress plugin that you activate in the bbPress plugins area that acts as a XML-RPC server and responds to a simple “say hello” type call. The second file goes in the root of your MU setup.

This test bypasses all the “bbpress_live/discover_pingback_server_uri()” stuff that might be giving you problems. If this works then the issue is most likely in that area and could be a host/server problem.

To load the test, first install the “oci-bb-sayhello.php” file to your bbPress install root in a folder called “my-plugins” (create the folder if it doesn’t exist). Then log into bbPress and activate the plugin. Next, drop the “oci-bp-sayhello.php” file into the root of our MU install so that you can navigate to it easily. Then load “your-site/oci-bp-sayhello.php” in a browser and see what the output is.

There are several possible points of failure if the test fails to authenticate the BuddyPress user that is created for the connection between BuddyPress and bbPress.

1) The BuddyPress connection username/password isn’t the same as the username/password that exists in bbPress. That username/password is stored in “wp_site_meta”.

2) The bbPress user is not an administrator.

Hi Sebastian, that really sounds great!

We have similar specs, here are my responses:

[blockquote]I will be creating a new Blog BP plugin that will be pulling all the posts, categories and comments straight from the user’s blog. [/blockquote] Doesn’t “all activity” already do that? Also, you mean straight from the users blogs (plural), right? That means, users’ blogs will show in your “home blog” right?

[blockquote]I will only be allowing one blog per user.[/blockquote] Me too, is that an existing setting?

[blockquote]Also I setup my BP installation not to use subdomains for blogs but folders.[/blockquote]Me too, seems cleaner and more appropriate for a “user,” also I couldn’t get it to install with the other method!

[blockquote]I will be looking to hook into BP’s url dispatcher to use subdomains for the public profiles and will be disallowing direct access to the actual users WP blogs (maybe using .htaccess rules) so that way blogs will look and feel like they belong to the profile just like the wire, friends and eventually galleries and not a separate/independent entity the way it currently works.[/blockquote]

I don’t know what you mean by disallowing access to the actual users WP blogs. Oh, now I get it…they don’t even “post” or “see” their actual blogs.

…Hmm…

Well, here’s something that may be a bit of a shortcut that you could try, it’s just that I don’t know how to do one step.

Just make the user blogs have the theme “buddy press home.” It looks like it works just fine. The only thing is that the user is then asked to configure widgets. If you could figure out how to allow only the main admin to configure the user blog template (including widgets), and if you could figure out how to activate and deactivate and “move around” those widgets on all user blogs simultaneously (all user blogs use one theme, and the settings are all set in one place by the global admin), then, it seems to me like we would be all set.

What do you think?

Best,

Dainis

I am using WMPU2.7 Buddypress RC1 and bbPress 1.0-Alpha-6

Hopefully someone can help me out here, it’s been 10 days, I’ve searched, this forum, the WPMU forum and the bbPress forum, and I feel like I’m going round in circles!

bbPress and WPMU/ Buddypress work fine as ‘stand alone’ applications, the challenge I am having is integrating bbPress into Buddypress.

I have gone through the whole of Trent’s great topic (https://buddypress.org/forums/topic.php?id=471) many times now, even removed bbPress and started all again.

What should on the face of it be a simple process, share users, share cookies, link via xmlrpc, seems incredibly complex, or else it’s the configuration of my hosting company that’s causing it!

I followed, Sam’s basic integration screencast (https://bbpress.org/forums/topic/basic-integration-screencast ), and all went smoothly, I can now logon and logoff from either WPMU or bbPress. I have also edited wp-config and bb-config as needed to use the same keys and to point to the same locations for the cookies.

However I can only access the admin/dashboard section in bbPress if I login in through bbPress, if I log in first via WPMU, the ‘admin’ link doesn’t work. I can access the dashboard of WPMU whichever way I log in.

In Sam’s screencast he talks about bbPress needing extra cookies and using bbpress-integration.1.0-alpha-4.1, I have tried with and without this plugin (which doesn’t appear to work when isntalled in mu-plugins/ ). I have also checked the cookies when logged in via bbPress and only see one extra cookie when actually in the dashboard / backoffice of bbPress.

Do I need this plugin?

Is this the way it should work, or should I be able to log in via WPMU and then go to bbPress and have access rights to the bbPress dashboard?

I have enabled xmlrpc and pingbacks in bbPress.

I have two key users “admin”, the main one created during wpmu install, which is also keymaster for bbPress and another with keymaster rights to bbPress and administration rights WPMU, it works the same for both.

Re Trent’s post, I have the plugin in my-plugins/buddypress-enable.php though there is some discussion as to wether it should be in my-plugins or bb-plugins – some guidance here please?

Also in step 6) where Trent says “Go into your main blog dashboard as the “site-admin” and go to the groups admin page.” I presume that with my configuration it should now read “Site Admin / bbPress forums”, If I click on the groups link, it gives me my list of already established groups to configure / edit. is my presumption correct?

I have configured the full path (with the “/”) and user details for bbPress in the “bbPress forums” option.

When I turn on Group Discussion, I don’t get a forum created in bbPress, nor can I post in ‘forum’ in the group in Buddypress, it comes up with “There was an error posting that topic.” not surprising really (no forum)

If I go to create a new group the box for “Enable discussion forum” is greyed out / missing replaced with a note that says” Attention Site Admin: Group forums require correct setup and configuration of a bbPress installation.”

Also from bbPress if I try to post I get “Warning: cannot yet handle MBCS in html_entity_decode()! in /home/sites/mydomain.com/public_html/forums/my-plugins/buddypress-enable.php on line 53 which I guess is because it’s not linked back. (I’m running MySQL/5.0.67 PHP/5.2.8 and PHP5/5.2.

Trent also suggested “check your bp_groups_groupmeta table” there was nothing in my data relating to forums.

I’ve tried it with and without the ” WordPress cookie integration speedup” and ” WordPress database integration speedup” in the bb-config.php file – it made no difference.

I’ve tried almost all I can think of,

@Burtadsit would your xmlrpc-test-rig be worth exploring? Do you have a download link for it?

“http://ourcommoninterest.org/downloads/xmlrpc-test-rig.zip&#8221; looks like it’s not there at the moment.

From here: http://umwblogs.org/wiki/index.php/Integrating_WPMu,_BuddyPress,_and_bbPress says:

You will need to install and activate the following plugins in your WPMu installation:

* bbPress Integration: “https://wordpress.org/extend/plugins/bbpress-integration/&#8221; This is essential, but keep in mind that this plugin is only useful if you are running bbPress version 1.0-alpha-4 or later.

* WPMU Enable bbPress Capabilities (0.1) “https://bbpress.org/plugins/topic/wpmu-enable-bbpress-capabilities/&#8221; : Enables bbPress member capabilities when a user is created within WPMU. This allows immediate login as a ‘member’ after a user is created in WPMU.

Do I actually need either of these with my confguration?

@johnjamesjacoby said “In theory, to create a post from within the Group forum, you should not need cookie integration, because the XMLRPC request happens very ajax-like behind the scenes and does not require for you as a specific user to be logged into both platforms.”

So any help would be much appreciated, Thanks.

It makes sense to me to give sub-blog owners a few templates, or just one. Really, I feel like too many templates will confuse the community, creating a lack of cohesiveness. Maybe I can have a few color schemes of the same template. Can my users upload templates? Should they be able to?

No, only you can. You’ll need to upload them to /wp-content/themes/.

I would like all activity to be presented on the main blog page. Basically, if anyone creates a sub-blog post, I would like that to be presented on the main page. Is that what the “all activity” widget does?

Yes.

I set things so that “blog owners” or “sub-blog owners” can’t install plugins, and I would like a nice, safe set of plugins and widgets that they can use without causing any damage. What about that WP plugin installer feature? Will someone gain access to it and break things?

You (as the admin) can upload plugins and widgets either via FTP (or similar) or via the Browser/Installer feature. You can also make plugins run on every site by putting them into the /wp-content/mu-plugins/ folder. The end user can activate or deactivate the plugins, but with the default user permissions, they don’t have access to the Browser/Installer page (I have just tested this).

1) bp widgets are available to all blogs. There isn’t a way in bp to restrict blog admins from using whatever widget is available to them.

2) The plugins that are located in /mu-plugins run on all blogs and don’t need activation by the site or blog admins. Plugins located in /plugins need to be activated on a blog by blog basis.

3) The avatars are located in /wp-content/blogs.dir/1/files/1/avatars/1 and should not be set to 777 but 755 and the apache user for your server must have write permission in that directory.

*Nothing* that you have control over should have 777 settings on your server. It’s a security hole.

Stupid people are the ones who don’t ask questions and live in ignorance.

This plugin works with wpmu 2.7 in following steps.

1. user manually registers.

2. activate account

3. go to profile, add openid

4. users can now login with their openid account(s)

OpenID login form is displayed on wp-login.php, but not on buddypress themed wp-signup, as it’s customized for buddypress.

This thread is not updated since 2 months ago, anyone else with tips or updates?

Your users have to register with wpmu and that means the main blog initially. If all you want is for them to be registered users in your community blog automatically then try this plugin: http://code.ourcommoninterest.org/2009/01/02/community-and-group-blogs-in-a-can/

Activate and configure that plugin on your community blog and when your users visit the blog for the first time they will become registered users at whatever level you set in the admin screen for the plugin.

I think that is what you want.

I’d go about this by making State a required profile field, and by hooking into the wpmu_activate_user action (triggers once a user *activates* their account). Depends on what exactly you want to do with regards to your notifications, but this should give you a starting place.

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

I’m having the same issue. But I have another problem (sorry for my bad english) … the other problem is that after croping the large image, and hit “continue”, it sends mi to a error page http://www.example.com/activate?key=7eceeb07e9659d4a&cropped=true … If i refresh, it goes back to homepage the user is registerd ok, and the avatar is ok …

the solve: “kkkforkkk: you are missing wp_nonce() calls. ” said Andy, but … where can i find this nonce calls? … i have uploades the latest version of bp and templates!

thanks!

Unfortunately not, at least right now.

What I consider the main reason for this, among the others, is that WPMU has a specific plugin directory devoted to “instant on” plugins, and BuddyPress relies on that specific ability within WPMU to activate itself and to load up all of the necessary files and functions.

You could, however, install WPMU and BuddyPress together, but then turn off the ability for users to make their own blogs. This will essentially make it operate like a WordPress.org install on the outside, with MU/BP’s sweet creamy insides.

We’ve got two themes going on in bp. The ‘blog’ theme and the member theme. bp ships with a home theme that is a widget framework. It serves as the theme that many activate as their ‘blog’ theme to run on the wpmu root blog. You’ll also see lots of standard WP themes being used and adapted to serving as the root blog theme. Lots of wonderful examples of what is possible are available.

Developing new member themes seem to be the challenging area that needs attention. Since the gurus are asking, I suggest you folks do some heavy lifting in that area.

Standard WP themes could also use a touch of bp flavor. Integration of some bp features into a WP theme might be nice. bp flavors such as:

– Profile and avatar support in blog posts, comments. When viewing an author or comment stream many times I’d like to leave a quick private note to somebody. Within the avatar/name/vcard block perhaps a link to send them a bp private message.

– Use of bp’s Groups for blog orientation. By orientation I mean that the blog theme should be constructed with multiple users in mind. As a given and not an afterthought. That the blog is a cooperative endeavor and should reflect that fact.

– Integration of the wire component as an ‘aside’ tool. General, quick comment area for members not tied to specific posts.

– A blog is also an individual’s way of expressing themselves yes. However in bp people have friends, belong to groups and have a personal activity stream. Perhaps some way of including that without launching the entire member profile for somebody would be nice.

I guess all my suggestions have to do with integrating useful bp features into standard WP themes so that the theme reflects to visitors they are just not in WP’s version of Kansas anymore. Which they aren’t. We don’t have to hit people over the head with social networking features, just include them in a natural and appropriate manner.

I had super-cache installed, with wpmu 2.7 and buddypress RC-1, and everything seemed to be working fine, except for I would get a 500 Internal Error on Wp-activate (when the new user clicks on the email link that is sent to them to activate the account). Everything else worked fine, wp-signup worked like a breeze, and all of my pages and posts were cached as they should be.

Once I uninstalled Super-Cache, wp-activate worked again fine. I uninstalled all of my mu-plugins (re-captcha, google analytics, buddypress redirect) and just put super cache and buddypress in there, and i still got the 500 internal error on wp-activate. When I removed it and added the others back in, everything works fine.

Any ideas? I’d love to have super cache working, but not at the expense of adding new members.

*/

require_once(WP_CONTENT_DIR . '/mu-plugins/bp-core.php');

function default_friend($user_id) {

global $wpdb, $bp;

$wpdb->query("INSERT INTO " . $bp . " ( initiator_user_id, friend_user_id, is_confirmed, is_limited, date_created ) VALUES (".$user_id.", ".get_option('bp-default-friend-id').", 1, 0, NOW())");

}

function default_friend_control() {

add_submenu_page("wpmu-admin.php", 'Default Friend', 'Default Friend', 8, 'bp-default-friend', 'default_friend_options');

}

function default_friend_options() {

if(isset($_POST)) {

$default_friend_id = $_POST;

update_option( 'bp-default-friend-id', $default_friend_id );

echo "<div id="message" class="updated fade">Options updated.</div>";

}

?>

<div class="wrap">

<h2><?php _e( 'Default Friend', 'buddypress' ) ?></h2>

<form action="<?php $_SERVER ?>" method="post" id="options">

<table class="form-table">

<tbody>

<tr>

<th scope="row">Default Friend ID:</th>

<td><input name="bp-default-friend-id" id="bp-default-friend-id" value="<?php echo get_option('bp-default-friend-id') ?>" />

</td>

</tr>

</tbody>

</table>

<p class="submit">

<input name="submitted" type="hidden" value="yes" />

<input type="submit" name="bp-default-friend" id="bp-default-friend" value="<?php _e( 'Save Settings', 'buddypress' ) ?>"/>

<?php wp_nonce_field( 'bp-default-friend') ?>

</form>

</div>

<?php

}

add_action('wpmu_activate_user', 'default_friend', 1, 1);

add_action('admin_menu', 'default_friend_control');

?>

Hi all,

I had the same problem of cropping and black box. First of all deactivate all your plugin.

then put the in the .htaccess file thoses comment

#uploaded files

#RewriteRule ^(.*/)?files/$ index.php [L]

RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*

#RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]

and then in the bp-core-avatars.php file within the mu-plugins/bp-core directory

replace the line

$newdir = path_join( ABSPATH, $path );

$newdir .= ‘/avatars/’ . $user_id . ‘/’;

by

$newdir = $path. ‘/avatars/’ . $user_id . ‘/’;

it ll work.

Then reactive step by step yours plugins you ll see those one who made the conflicts

Have so fun

from Martinique