BuddyPress.org

@erich73, you’re welcome. Do share how it’s working with you in WP 3.0

In line with the topic @anointed started a week++ ago, methinks that BP is facing a big mountain made of different WP/MU versions and making it work for all. In that line, might I suggest that Automattic allow @apeatling to concentrate on BuddyPress and be more informative about the direction of BuddyPress – less surprises the better

At this time, with BP 1.2.4.1, there are at least 11 configurations of WP/MU versions to make pretty with:

New Installs
1. WP 3.0 (Single site)
2. WP 3.0 (Multisite – Subdomain)
3. WP 3.0 (Multisite – Subdirectory)
Existing Installs
4. WP 2.9.2
5. WP 2.9.2 upgraded to WP 3.0 (Single Site)
6. WP 2.9.2 upgraded to WP 3.0 (Multisite – Subdomain)
7. WP 2.9.2 upgraded to WP 3.0 (Multisite – Subdirectory)
8. WPMU 2.9.2 Subdomain
9. WPMU 2.9.2 Subdirectory
10. WPMU 2.9.2 Subdomain upgraded to WP 3.0 (Multisite auto)
11. WPMU 2.9.2 Subdirectory upgraded to WP 3.0 (Multisite auto)

Notes:
a. Add Server/OS to the mix – Windows, Linux, shared hosting vs VPS hosting, etc.
b. Add configuration where BP is installed in subsite other than main site
c. Add single WP configs (per wp.org forums) where WP is in directory and index.php in root – have to tell them whether that config will work with BP at all or not.
d. Media uploads – WP 2.9.2 and new WP 3.0 (main site) installations upload media to wp-contents/uploads folder while WPMU 2.9.2 and WP 3.0 (subsites) installations upload media to wp-contents/blogs.dir folder. Member and Group Avatar uploads – same as above (a) but in respective /avatars/ and /group-avatars/ folders.
e. Many plugin and theme developers would rather wait for BP 1.3 where components will be rendered as Pages so that time won’t be wasted on plugin or theme development which will be considered “obsolete” in a few weeks or so, pretty much like what happened to plugins and themes from BP 1.1.3 to BP 1.2
e. I’m sure many would be able to add some more here, etc. etc. etc.

So when BP 1.3 rolls out and it requires WP 3.0, there’ll only be six configurations left from above list as per a thread I read not to expect WP 3.1 anytime soon. Add to that the major changes in how BP renders components as Pages which mixes with “regular” WordPress Pages, BuddyPress has become a test of endurance that requires a lot of willing developers to go through the angst of getting a BP site just as one wants it for specific installation. Otherwise, Elgg or Drupal or phpFox et al would have been installed in the first place. Just my 2 cents.

Then via FTP remove all of your plugins (including BP) in your plugin folder. You can just drop them onto your local machine. Now after that try accessing your WP dashboard again. Now what?

@jeffsayre , you and many others here have been spot on about the BuddyPress leadership as-is. I particularly liked the notion of ‘proactive communication’ (and the lack thereof) so much that I felt compelled to repeat it.

@paulhastings0 about electing leaders, I just don’t think this is a good idea. There’s just too much to factor in when core development needs and relationships come into play. I’d argue that thanks to the combined user friendliness of WP&BP, this community consists in large of low-tech pseudo-developers such as myself, who are able to build websites and great communities with BuddyPress, but wouldn’t find our way home if we ventured far into any given .php file.

Sure, if it came to a vote I’d think about who in this community I find admirable, productive, dedicated and so on, and I’d put my vote in. But what is my vote worth in such a big matter anyways, when what it really comes down to, besides the obvious qualities of a community hero, is the prospective developer/manager’s ability to communicate and work on the same wavelength as is established in the core team already.

I don’t fear for BuddyPress; I see a very bright future for it and anyone who takes the leap to invest (freely interpreted). This has been an important discussion none the less, and as if the lesson learned was not clear as day already, I intend to spell it out:

BuddyPress development needs an extra layer of transparency. Front-line fighters of the community should be trusted to tap into the ‘inner loop’. As people who’s ‘been around the block’ (see, only mature people would refer to themselves in such a manner) they can be expected to handle sensitive information with care, knowing what to share and when to share it. Whenever the foremost figures of a community are absent, members immediately start looking for whoever is next in line, a search ideally concluded with “oh, silly me, naturally it’s that nice person who’s presence I took notice of from the start”.

@gregfielding Maybe for you BP is about the blogs. For my BP install it’s about the groups. Everyone uses BP a little different, so it’s hard to make broad statements like that.

Howdy.

Just a note to say hi, and if BuddyPress dies, that would be sad because it does have quite a bit of potential.

I’m developing a project around it for a small school at the moment, and its the perfect thing to allow parents to communicate with each other, while teachers can post homework assignments.

I think the system has potential for lots and lots of educational instiutions, and there should maybe be some thought amongst the team about spinning it off in that direction since another WordPress tech, WordPress MU… has been geared to those places, and this would perhaps attract even more developers to the project.

Also, if people need to work to eat, maybe we can do a kick-starter fund to get some paid people working on it to keep it going, I’d happily donate some cash.

@kevin and @ MW, That’s exactly what i want to do too. i’ve installed WP 3.0 with multisite enabled and the last version of buddypress, everything is ok except i don’t know how to allow any user to create a blog. How can we do that? Can anyone tell us? Thanks!!

@erich73, have not tested this with WP 3.0 but @sbrajesh has a free plugin for BP 1.2 – The bp-wire for putting the Buddypress wire back to Buddypress 1.2 or method by which you could Use Activity as Wire as well

Ning defines blogs differently than how we at WordPress/BuddyPress do. A Ning site member can click on a link “Blog” and Ning’s post panel. You can try using Jet QuickPress – https://wordpress.org/extend/plugins/jet-quickpress/ which adds “a “Quickpress” submenu you can find in bp admin bar > My Accounts > Blogs > QuickPress from which you can easily add a post to any of your blogs

Just a thought: the plugin, in effect, can render a Multi-Author BP site without adding subsites and without allowing access to the dashboard because members can post from the front and click on categories and add tags there as well. Then, one can create a customized member profile page to have that link to blog posting and then render the latest posts of each individual member .

Yeah, I hope you made a backup of everything before you started.

Can you still access your WordPress Dashboard? If you can then go to your themes panel and first try choosing another theme for your site. Can you confirm if you can do this?

@techguy BigDoor looks awesome, but it’s still in Beta. I’m doing a custom build for a client’s achievements and medals, with cubepoints backing the point mechanic.

The big con for me is that bigdoor’s API access costs money after a certain point, and if the site becomes huge, that could be a cost sink for the client. I would do it for a smaller or personal site, or one where the money incentive is BIG.

I had the same question as Kevin – how can users create their own blogs? from the showcase sites especially the one on EcoLiving here http://helloecoliving.com/hello-eco-living-blogs/ they have the option Create your own blog. so I thought it was part of BuddyPress but I guess not.

Did you disable all other plugins before uploading the BP 1.2.4 folder?

does this mean that BuddyPress is not compatibe with WP 3.0 ?
Will the BP-GroupBlog-Plugin still work ?

oops @andy could you please forward all recent @mentions to @apeatling
@mikepratt It is surprising the amount of talent available , and that all appear to have been around the block a few times on a sidenote and to add a little levity to the thread Jeff Sayre wrote a interesting little post on his blog on ageism and a project he was recruiting for.

I made a “solution” until someone have a better suggestion!

With file “bp-fbconnect.php” explained above:
if ( !$height ) {
if ( ‘thumb’ == $type )
$height = constant( ‘BP_AVATAR_THUMB_HEIGHT’ );
else
$height = constant( ‘BP_AVATAR_FULL_HEIGHT’ );
}

I just “removed” it completely by adding /* */ like this:

/*
if ( !$height ) {
if ( ‘thumb’ == $type )
$height = constant( ‘BP_AVATAR_THUMB_HEIGHT’ );
else
$height = constant( ‘BP_AVATAR_FULL_HEIGHT’ );
}
*/

In the “common.php” file found in the “wp-facebookconnect” folder go to line -66 and add “$dims2” like this:
function render_fb_profile_pic($user, $dims = 32, $dims2 = 10, $size = ‘square’ ) {

And change width=”{$dims}px” on line -68 to:
width=”{$dims2}px”

This was my quick “solution” using the standard bp-theme! Not the best but better than having the error message.

Btw, the correct username is @apeatling, not @andy (that poor guy is getting overloaded with a bunch of non-relevant notifications. )

Ah, you’re referring to: https://buddypress.org/community/groups/buddypress-ajax-chat/