BuddyPress.org

i’d like to see the whole activity stream become a bit more robust – generic in use but more powerful api options

– access control (who, what – can update, read am AS record – fine granular framework from users, groups, plugins, component, types) – right now its a bit clunky to remove certain items and no way to block others (ie, i like a plugin’s functionality but i don’t care for the activity record, i want to block certain groups from updates, or block certain activity types to be displayed, etc)

this one may be outside the criteria but the whole bbpress <-> bp thing. IMHO – ramp up the AS to handle forum content. (already have commenting, threading, etc – i don’t see importance of bbpress hiding under the covers, even if it will become a wp plugin. so much duplicate functionality being used and another layer of dependencies)

BP => like Firefox and Burger King – I love extensibility and having it my way.

No bugs found yet (except the conflict with Simple Tags that I reported in the 0.3 thread.

There is a conflict with the Simple Tags plugin (http://redmine.beapi.fr/projects/show/simple-tags). In the admin > manage links, under each link except the fist one I get the following errors:

Warning: array_keys() [function.array-keys]: The first argument should be an array in [path]/wp-content/plugins/simple-tags/inc/client.php on line 1310

Warning: shuffle() expects parameter 1 to be array, null given in [path]//wp-content/plugins/simple-tags/inc/client.php on line 1311

Warning: Invalid argument supplied for foreach() in[path]//wp-content/plugins/simple-tags/inc/client.php on line 1312

This error also occurs in BuddyPress-Links 0.4.x.

buddypress > Facebook

Buddypress is the tool that I use to bring friends and friends of friends together.

The emphasis of my community is primarily blogging. It’s for the people who’ve never had a Facebook account…. and for the people who use Facebook, Twitter, Buzz and more. So for us Buddypress is the superglue that pulls WPMU (soon to be WPMS) together.

Forgot to mention, when I click the link for the search page, it redirects back to the homepage.

Wow ! The” what” and the “how” the same day on the same forum: the hazards of life ?

https://buddypress.org/forums/topic/so-your-bp-site-is-up-now-how-to-bring-the-people-in-and-start-using-it

@katendarcy: Could you elaborate just a little bit on your previous post to @jamesyeah? I am having the same problem with not being able to select a location field. I’ve already set up a registration form with fields for city state and zip code, and included the lat and long fields specified in the plugin install directions.

Thanks!

I’ve tested it on single WP and WPMU and it works 100%. Same as @Bpisimone. No bugs found. I had a problem with 0.3.2 where I couldn’t see the link votes when using the filter on specific links but it works now. Well done MrMaz!

One question. What’s the difference between the filters “highest rated” and “most votes”?

A tool to start your own social niche network.

A niche could be everything and buddypress should be easy to customize and expand so it could adopt to all of this demands. Thats why i like that Andy decided to get MrMaz on board. He knows where the limits of the actual API are because Buddypress Links pushed it to the limits.

I guess a crucial point could be to identify the “missing core functionality that is deemed to be of a high value to the BuddyPress community and to plugin developers”.

There could be a public poll, but at the end the developers should identify what is most important … they have more knowledge and a better foresight as a common user like me.

I guess good privacy and access control will be something to look at with highest priority.

Also, can I put in a vote that this be extensible? Like that GSoC project for the Report/Ignore plugin, the Ratings system should really be content agnostic – whether you put the rating interface on the activity stream, forum post, blog post, or other BP “component” type.

And speaking of that, there is a great “rating” system in MrMaz’s Links plugin. So not sure where all of this is going, but one would think your reputation as a BP user would be a combination of your forum posts, blog posts, and links, right?

https://wordpress.org/extend/plugins/buddypress-links

Social networking really should be about the people, so all BuddyPress should do is deliver the basics that are needed to build a community. That would basically be all the various components that we already have. Because of legal restrictions in a lot of countries I’d only add a privacy component to the core. Any other feature would be better implemented as a plugin. We could even have canonical plugins, just like WP. Keep the core as lean and mean as possible…

@thelandman

Read this:

https://buddypress.org/forums/topic/adminbar-in-the-footer

Let’s set up something here? What do you think?

http://www.kickstarter.com/start

But will it melt our heads?

I think that in some ways the question ‘what is BuddyPress’ jumps the gun at this stage. The question might rather be phrased ‘what could BuddyPress become once we’ve rewritten the core and API’? My guess is that BuddyPress will grow organically in ways that we cannot possibly foresee at this juncture. That’s the one of the strengths of Open Source projects.

Is it too late to start this process? Nah mate! Look at some other Open Source projects – Gallery photo album is on it’s second rewrite. Elgg developers not only rewrote the core/API they made the 1.0 totally incompatible with previous beta versions thus leaving a whole bunch of implementors high and dry (which is why I’m moving to BP)! My question is more, who is going to lead this process — you, Mr Maz? — and what role will Automattic have?

One issue that might be addressed in the core is your philosophy with regard to access controls. One of the built-in features of Elgg 0.9 which I found superficially attractive was the ability to set an access control on any object — blog post, file upload (but not comment) — and to add arbitrary access controls at the user level. However, in practice this often didn’t work out very well. Members of a closed Community blog had to remember to apply ‘community only access’ to each post that they made, they would frequently forget and thus expose content unintentionally. But I do think that looking at this example, and also how Mahara handles it’s file and blog access can help inform the sorts of access features we would like to see exposed by the API.

What might BuddyPress become? With flexible group and access control features it could become a premier eportfolio solution for example. Just my 2 penneth ………

Hey Foxly, I looked through those files:

bp-album-templatetags.php

sub-album-templatetags.php

sub-media-templatetags.php

sub-meta-templatetags.php

And the problem is that it seems almost like a redirect or something, the actual image is found in:

/wp-content/blogs.dir/1/files/album/12/filename.jpg

This function here bp_album_picture_url() for example returns:

/files/album/12/filename.jpg

From what i’ve tested this redirect (I don’t know how it works exactly) causes problems with certain PHP Scripts and I believe it will cause problems with Facebook and Digg Sharing as well.

Oh BTW Right Click + Save doesn’t work on the default BuddyPress Album Template because the hyperlinks hovering over the image itself blocks the users ability to save the image to their computer (unless of course they are a bit more computer savvy)

EDIT:

Actually it looks like a WordPress MU Issue:

see here: https://mu.wordpress.org/forums/topic/12397

the blogs.dir directory is set to “nobody users” group so that is what is causing problems with the script, anyone been able to fix that problem yet?

Thanks for starting the conversation, MrMaz.

I want to see BP more as a framework for social tools rather than the end-all-be-all for social networking. Like WP itself, the real power of BP is in its extensibility. (Which is what makes the conversation about the API all the more important.)

It seems to me that throughout the development of BP, there have been two directions of movement: one is to consolidate functionality (as with the recent rolling of some blog related tracking into the activity stream) and the other is to add functionality. The two aren’t inherently at odds, but they do have a tendency to fight against one another. For ease of development, solidity of platform, etc, my tendency would be to err in favor of consolidation. The discussion that was floated a few months ago about moving more kinds of content creation into the activity stream is one example of this. I’m not really 1337 enough to say what this means from the point of view of scalability, but I can say that having fewer points of input/output make third-party plugin development a lot easier.

So, I were to think of the BP toolkit as a swiss army knife, I would want BP to be the handle and maybe the big blade or two. Corkscrews, nail clippers, can openers and stuff like that are cool, but they should be options.

I’d like to stop making comparisons to Facebook. (yes, mea culpa ;P)

It can be bigger (or smaller as in tight-knit)

it can be better

It can be *different*

than Facebook.

I don’t think we’re looking for a facebook clone of any sort. Not long term.

https://wordpress.org/extend/plugins/buddypress-admin-bar-mods/