BuddyPress.org

Version 0.1.5-alpha

at Backend – Options – Maps Sizes, I get the following Warning:

Warning: Invalid argument supplied for foreach() in …/wp-content/plugins/buddypress-maps/bp-maps-admin.php on line 278

and the Drop-Down is emty

@zageek

Yes, usability is a big challenge.

Here’s my 10 cents worth. Note: I come from the perspective of generally seeing BuddyPress as a tool to implement vertical social networks that would typically connect with / enhance Facebook and other social platforms.

What you are saying is very reasonable to debate. I’m not sure it’s a role for the core BuddyPress project (or a fork thereof), but can certainly see the need for it in a large number of BuddyPress based sites.

The Challenge

To build the system you suggest, the remaining challenge is how to handle blogs whilst appearing not to give the user a separate admin system (the rest is all handled by the front end already).

I understand where you are coming from, and also have clients for whom this is a major headache.

The core BuddyPress / WordPress needs to be a broad flexible system, to allow us to build as wide a range of systems as possible (as our clients / users demand). Unfortunately, as you point out, for a lot of developments this provides a lot of ‘excess interface’ that leads to end user confusion.

Our challenge as developers is, therefore, to build on BuddyPress (or take away from BuddyPress) to ensure we present a clean consistent interface to users in our finished developments.

Dealing with blogs

If the site is going to give end users a rich blog feature set (e.g. choosing themes, positioning widgets, and creating category structures), then I don’t see how we can avoid exposing the wp backend.

In this situation though, you could perhaps re-theme the admin backend to ensure a consistent look and feel with the front end. This is a lot of work, and we don’t go this far with our own site developments, instead we opt for the very partial solution of just rebranding the backend (using plugins from WPMUDEV).

If you are only going to allow the end users to have minimal blog features (e.g. posting a story), then a clean front end only solution is more viable (have you looked at plugins such as: https://wordpress.org/extend/plugins/front-end-editor/ ?)

Or, if we are not going to offer blogs, then simply turn them off.

I thought I’d read something on ‘post from frontend’ features in WordPress 3.0, but might have been dreaming it.

@r-a-y i upgraded to latest and the plugin died. work great with previous version.

WP single 2.9.2 BP 1.2

EDIT: just realized that even though you auto upgrade you have to go back and change the folder name

This plugin partially works with WP 2.9.2 and Buddypress 1.2

Pasting a link does embed the video but it also causes an error. Here is a screenshot… https://i.imgur.com/XCvPv.png

Since this forum is meant to discuss possible enhancements for future BuddyPress versions in 2010, the idea of forking the project is beyond scope. You of course are free to continue discussing this topic but it might be better to start a new thread in the Miscellaneous Forums.

As to this example:

Lets say if i want to use Buddypress to set up an organic farming community for example I am going to have many of my users getting confused with having a backend and a front end and all of the options and admin stuff in the backend.

The only reason users would need access to the backend is if the Site Admin has set up their BuddyPress community to allow users to have their own blogs. If the mulitblog feature is not enabled, then users only have access to the frontend menus to set options and navigate the network. Also, the Site Admin could choose to build their community on the single-user version of WordPress. Then offering blogs to users is not even an option.

Whereas your assertion that

…stripping out the WP centric features surely won’t be an issue in the context of running a social network.

might be the case from a user’s perspective, it is a huge issue with regards to the amount of programming and code refactoring that would be required.

I can state with a high-degree of certainty that Andy nor Automattic will not be forking their own creations. The only way I could see that happening is if a few Automattic employees break off and form their own shop.

Why wait for someone else to do it? As I said in my first post in this thread, forking any OS project is a lot of work, but you are free to do so as long as you follow the GPL. If you think you have a unique, under-served vision for the platform, form a team and do it.

@grosbouff – Thank you!

I´m using BP Maps and BP Maps Profile and it works like a charm.

Will you put it up for localization, at least for user side? I will be happy to contribute with a Swedish translation.

BuddyPress Links 0.3 works with 1.2 including single WP:

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

Here is my blog post about the release:

http://marshallsorenson.com/post/buddypress-links-0-3-released

Jehy suggested the plugin Register Users Only 2. It has worked well in my install. Hope this helps.

https://buddypress.org/forums/topic/limiting-access-to-registered-users#post-38303

Possibly some people subscribed to this topic would like to know that i modified my access restriction plugin and now it works with buddypress 1.2.

Please try

https://wordpress.org/extend/plugins/registered-users-only-2/

Possibly some people subscribed to this topic would like to know that i modified my access restriction plugin and now it works with buddypress 1.2.

Please try

https://wordpress.org/extend/plugins/registered-users-only-2/

Hello. I just corrected registered-users-only, and it sould work fine with buddypress

Your tests and feedback are welcome:

https://wordpress.org/extend/plugins/registered-users-only-2/

Accoring to https://wordpress.org/extend/plugins/bp-member-map/changelog/

yes and no

JJJ?

Great question. Jeff Sayre had the privacy plugin of 1.1.x but won’t release a version for 1.2 just yet.

http://jeffsayre.com/2009/12/05/buddypress-privacy-component-released/comment-page-1/#comment-531

I’m confident, when released, it will provide some much needed privacy to BP.

I’ve heard that the following plugins may help bring some privacy to BP, but I haven’t heard which one users find the most effective or are compatible with BP 1.2:

https://wordpress.org/extend/plugins/registered-users-only-2/

https://wordpress.org/extend/plugins/registered-users-only/

https://wordpress.org/extend/plugins/members-only/

Grosbouff, are you aware of the Geo Mashup plugin. Couldn’t you leverage that?

I installed and activated Geo Mashup site-wide, but then it asks all the member blogs for their own Google API code in the wp-admin, which is annoying and will confuse many users.

Haven’t had time to test your plugin yet, but if it does the same as Geo Mashup, I’d rather have a cleaned up BP-ready version of Geo Mashup.

Deleting of a wiki-comment when I get this error message:

Warning: include(…/wp-content/plugins/bp-groupwiki/bp-groupwiki.inc.php) [function.include]: failed to open stream: No such file or directory in /www/htdocs/tolih/tradiDB3/wp-content/plugins/buddypress-group-wiki/content-pages/wiki-comment-options.php on line 19

Warning: include() [function.include]: Failed opening (…/wp-content/plugins/bp-groupwiki/bp-groupwiki.inc.php’ for inclusion (include_path=’.:/usr/share/php:..’) in …/wp-content/plugins/buddypress-group-wiki/content-pages/wiki-comment-options.php on line 19

Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/buddypress-group-wiki/content-pages/wiki-comment-options.php:19) in …/wp-includes/pluggable.php on line 868

Grosbouff, looking great. Will be testing it tonight. Cheers.

I’m not asking non-coders to do it, I’m suggesting ways in which coders can do it and submit patches so *everyone* can benefit.

@raoulduke, I did get Posthaste working. I had the tag in the wrong place. It really needs to be right before the loop.

P2, Posthaste, the TDO Mini Forms plugin all work fine on regular blog index pages, but I can’t get any of them to work on the Group Blog. There is a referral check problem or the form can’t find the right blog ID.