BuddyPress.org

Since you’re asking, I think maybe you should have let Andy announce this when it was time.

Now that the cat is out of the bag, I think it only makes sense to offer BuddyPress to the widest audience. In my opinion, BuddyPress does what everyone wishes WordPress would have done in the first place, so I feel like this was inevitable and a very good thing.

Btw David, I was the tall skinny guy that helped you get the projector working at your presentation. :wave:

https://core.trac.wordpress.org/ticket/9245

OK, so this is a core WordPress setting. It’s in /wp-admin/includes/image.php – specifically, the call to imagejpeg on line 71. http://php.net/imagejpeg has an optional third argument $quality. It defaults to 75 (0 being worse, 100 being best). If urgent I suggest changing this file for the interim.

Elsewhere in WordPresss, /wp-includes/media.php, we have this:

If (!imagejpeg( $newimage, $destfilename, apply_filters( 'jpeg_quality', $jpeg_quality ) ) )

return new WP_Error('resize_path_invalid', __( 'Resize path invalid' ));

I’ll put a ticket on the WordPress trac to see if we can get this filter added to the call in image.php.

*EDIT*: this is a core WordPress file, not MU.

Login to WordPress admin, go to Site Admin, Options, scroll to the bottom, under Menu, activate Plugins.

Hi, you need to login to your wordpress admin, go to Site Admin, Options, scroll to the very bottom, under Menus, activate Plugins. Not sure why default is set to off.

https://buddypress.org/blog/2009/02/rc-1-new-wordpress-mu-functionality/

There are some major changes happening to WPMU, so Andy mentions he is waiting until those changes are complete and then release the final alongside WPMU.

Trent

@brandtd, back from the dead… Looks good and I like the colors a lot.

Something I noticed is that the page links in your main navigation start with “www.” when it doesn’t need it. If you’re using RC1 then that is hard coded and you can just omit that and be good to go.

@Andy, question that I didn’t see asked… For the recent forum widget, are you using the existing widget for non-mu WordPress, or did you make a special one for BuddyPress?

I’ve corrected some bugs now. Please try the latest version, WP Google Maps – 2.0b2, that you can download at http://www.ezbizniz.com/wordpress-plugins/google-maps

wp commerce works fine in mu what are you talking about

A majority of the plugins do work, and it’s up to each individual author or admin to adjust the plugins that don’t.

The obvious plugin issue with MU is fixed in the trunk from what I understand, so it’s only a matter of time before MU gets bumped to 2.7.1 also.

So what it sounds like you’re saying is that you know the answer to your question, but you don’t really like it so you want to vent a little.

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

I would like to see the ability for users to be able to personalise their profile page, with this I mean them being able to pick ‘boxes’ with content (say, my groups, my friends, online friends, personal info, etc sort of like widgets, but picked by each user) and place them on their profile, perhaps able to move them around ajax style (and hide/minimize/maximize them) like in the WordPress backend dashboard.

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.

perhaps I posted wrong the line:

<?php bp_friend_last_content_update() ?>

doesn’t do much, you’ll need to decide what material you want to display there.. I assume this is going to be the “home” theme of the wordpress mu right?

I recommend copying all of the contents of BuddyPress Home to a new directory, modifying the style.css to a new name, comparing your existing WP header.php/footer.php files to the ones in your new directory, taking out all the WordPress specific PHP function references and replacing them WordPress MU/BuddyPress ones. Tedious, but effective.

I found that the main hurdle when doing this kind of migration (for me) was letting go of my old WordPress ways of doing things. I.E. no longer using the page widget as my main navigation menu, etc… Which you can still do if you want to, there’s nothing stopping you. The functions are still the same, but you’ll still want to use the BuddyPress home theme as your starting point, as it gives you the building blocks towards integrating your existing theme with the new platform.

I’m also trying to integrate ecommerce capabilities into Buddy Press – but for a completely different reason.

We are setting up a campaign website on the MU platform to use the strength of WP’s CMS for the blog, new, media parts of the site – and then utilize MU and BuddyPress to allow campaigners / supports a place to communicate and interact. (similar to Barak’s “my.BarakObama.com”)

We want to allow supports to donate to the campaign and track there donations on their member pages. I’m looking into a 3rd Party Member management platform called “amember” (www.amember.com) as it has a wordpress integration plugin and offers the ability to sell “subscription” products. It is only tested with the standard version of WP – not MU, so I’m running into some database issues where the wp_1_ prefix is throwing me for a loop. (I’m not the best PHP programmer)

Any thoughts on using these two platforms together? Is there a better solution?

hempsworth, to be honest, this sounds more like a forum functionality than a blog to me. WordPress has never really had this type of straight forward user based permissions functionality, and while I can say that I think it sure could use it, I will also admit publically that I’m probably not the guy for the job. I think ideas like this should be added as feature requests to the trac, because they’re outside of the current 1.0 scope of BuddyPress, and would also involve some changes to WordPressMU.

Burt, I will take a gander. Also, you think possible to add an option to make the members of the group all editors? Could sort of have a blog/wiki that way.

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!””