BuddyPress.org

@gregfielding

https://wordpress.org/extend/plugins/enable-oembed-discovery/

@Erich73-

Haha! I appreciate the thought. I’m sure Automattic is able to afford to buy many things! I have no issue with Automattic. I do not expect them to pay me.

@everyone

My code, like any other GPLed theme or plugin is freely available for all to use. So, if Automattic wants to merge my code into BP core, I would be honored and not expect anything else in return.

I hope that my posts (in this thread and on my website concerning this issue) do not come across as me being bitter. That is not the case.

I fully support and believe in the Open Source model as expressed via the GPL. I also believe in giving back to those Open Source projects from which you have benefited. I of course have done that with the hundreds of hours I’ve donated as a moderator on these forums.

The referenced-to post above was just my attempt to try to figure out a possible way where I could actually earn part of my living by creating great-quality plugins for the WordPress / BuddyPress community. I think talented programmers should be able to do that without having to resort to consulting. I have no interest in providing consulting services. I owned a consulting company for 7 years. It was great, but I have no need or intention of going back down that road.

So, enough said with all of this stuff about me and my needs. I appreciate people’s concerns and suggestions.

Let’s put this thread back on track. Please try to limit your comments to the future of privacy in BuddyPress and not about me!

@idotter-

Eventually my plugin will encompass group and blog privacy as well.

@paulhastings0-

The graph represents about $125 of funding–which is close to my original goal!

I never expected to achieve the funding goal. That post was for two reasons: an experiment to see if raising development funds was even feasible; an awareness campaign to get people talking and thinking about plugin developers and the vast amount of time that they put into WordPress/Buddyress projects so that the community can benefit from their work.

The goal is an honest assessment of the amount of time (which is then converted to dollars) that I will be required to put into the project in 2010–coding and supporting the plugin. It also covers some of my time already spent on coding the plugin.

As I state in that post, I’m already committed to bringing my privacy plugin up to date to work with BP version 1.2. When that will happen is the question. I am working on it, but not full time as I have another project that has top priority (my startup). Just like anyone else, I must focus most of my efforts on activities that will help me actually earn a living.

Once my BP 1.2-compatible privacy plugin is released, I’m not sure where it will go from there. We will see. Of course, if my privacy plugin gets merged into core (in some form or another), that would be great!

Burt Adsit, a past forum moderator and talented developer, created a plugin that did exactly what you are suggesting. It is woefully out of date. I believe it only works with BP V 1.0. But, some other talented developer could possibly use Burt’s code, adapting it to the current version of BP.

https://wordpress.org/extend/plugins/bpcontents/

@Xevo, I’m pretty sure Erich73 was not asking for a poll plugin. I think his comment was about the relative pointlessness of open polls for new features, when there are still many core issues that should be fixed first.

I remember we’ve gone through this over six months ago, also with a poll and promises that certain features, like privacy, would become core in version 1.2 and 1.3. Very little of that has materialized.

… I can see that users of wordpress/buddypress wanting the wp-admin to be only for admins as the name suggests and keep the users off the creepy admin panel.

Absolutely. That’s why I’m trying to sort out front-end posting with P2 and/or Posthaste. Raoulduke is working on it as well.

@ 21dcb

I believe that Polls should be a plugin made by some third party plugin developer. That’s why I said that, I do believe some buddypress users could use something like that. Also seeing that Erich said it was in the development list for 1.3, I figured it was for the core buddypress.

Also, Facebook was build off the ground, I can see that users of wordpress/buddypress wanting the wp-admin to be only for admins as the name suggests and keep the users off the creepy admin panel.

@ DJPaul

So on which items the most votes are, is going to be developed first?

Totally agree, Erich73.

I’d also add privacy (making parts members-only etc.), another core feature that was promised a year ago and again after polling last Fall, but disappeared from the priority list for 1.2 and 1.3. Poor Jeff Sayre has been struggling with that without any support from Automattic.

‘User-Blogs-Posts from Front-end’ can be done in most places by integrating the P2 theme or using the Posthaste plugin. Both work fine on regular blog index/home pages.

I’m trying to get it to work on the group blog homepage. No luck so far. Will post for download today or tomorrow two versions of the excellent bp-groupblog with P2 and Posthaste code integrated, as far as I can figure them out. I will need some help fixing them.

Hey r-a-y, than you for your reply

I have some little questions, after i’ve read all topics around here (i guess) about bbpress and buddypress combined:

– To have a forum as it is on buddypress.org/forums, you need to install bbpress seperatly and integrate it with wordpress. Does this way allow the Group Forums, as if you install bbpress within buddypress (not seperaly) ? (maybe there is a plugin for that as far as i know, but know nothing about its stability with the new buddypress);

– I’ve installed bbpress within buddypress, (not a seperate bbpress install). I made a group called Forums to check if forum will be enabled in it…and yes it is as you can see here. http://myislamicblog.com/groups/forums/forum/

But the problem is if you noticed, the Forums Link on the right menu doesnt appear next to blogs and groups.

Any ideas?

Thank you in advance!

Ok people, step back from your keyboards and take a deep breath.

1) The ‘ideas’ forum collects any ideas that people want to see in future BP version.

2) After some period of time, I am going to make a list of all the ideas. I am going to take it to a http://bpdevel.wordpress.com/ BuddyPress dev chat, and those present (everyone is welcome) will help decide which of those ideas to go into a poll on this website.

3) Everyone can then go to the poll on this website and vote what they would like to see in BP version 1.3, 1.4, and so on. Results will be announced by Andy Peatling and the Roadmap updated.

This is very similar to what happened around the 1.0 release.

Like what 21cdb said:

Humans always looking out for their own interests, thats natural behaviour, but we should always keep in mind to respect interests of the public and of the parties concerned as well.

A poll is a great way to determine what the public needs are. I believe it will give the main developers good impressions in which directions they should focus in the future.

For anyone following the thread to date: Armand Morin’s question (how to add the BuddyPress Nav to the theme) gets answered here: https://buddypress.org/forums/topic/creating-nav-bar

Just install bbpress the old fashion way and do a wordpress intergration.

I’ve had a home.php and a blog page working in custom child themes of bp-default since 1.2 trunk and in bp-sn-parent before that, I did it this way:

1. create home.php as usual

2. create header-home.php to protect home.php

– made it when in 1.2trunk a conditional statement inserted in header.php limited home page to blog page or activities page and kicked out my home.php

– in home.php call header-home.php with

<?php get_header('home'); ?>

3. create “blog page” with pagination

– 2nd option in this post http://www.nathanrice.net/blog/creating-a-blog-page-with-paging/

– Make sure you delete spaces between <?php after copying codes from that post

Except for the hiccup in #2 above, home.php, a WordPress template file has been respected in BuddyPress custom child themes and it overrode any home.php file in parent theme.

Cheers.

Try installing the BP backward compatibility plugin if your old BP theme / plugins relied on BP 1.1.3 code:

https://wordpress.org/extend/plugins/buddypress-backwards-compatibility/

The forums on GoFastBargains.com is using the internal forums component in BuddyPress. No integration is needed with anything else.

This is how it’s done:

1) Install WordPress

2) Install BuddyPress

3) Enable forums component in BuddyPress

4) Smile! You’re done!

oEmbed for BP does one thing very simple – it utilizes WordPress’ own oEmbed class — type in a plain-text oEmbeddable URL and voila! — there are no plans to do anything special in the future (like categorization, etc).

I wholeheartedly endorse MrMaz’s BP Links plugin; I have stated this in other posts and I”ll say it again – BP-Links will be the definitive rich embedding plugin for BP.

We have briefly talked privately about manipulating the activity stream for embedding content (btw MrMaz, let me know if you need a sounding board for the next version of BP-Links!).

He has some neat things planned including plugging into the “What’s New” box, which will solve the “quick and easy embedding” issue Mike has talked about above.

At the end of the day, the cool thing is you have choices!

it all depends on your BP network’s needs.

Try using the wordpress loop..having tried this yet but it should worked in theory to block the button from subscribers. This should really be built into buddypres though.

<?php if ( current_user_can(‘edit_post’) ) {

// button goes here

} ?>

I liked Modemlooper’s idea to have such separated widget home page. But i was interested in to have more columns.

I have modified the theme with 4 up to 5 columns. The 5th column/ section is deactivated by default within the syle.css (display: none;) It is easy to remove this line and to modify the width-pixel sizes of the other columns if it is needed. I have sent the new theme to the wordpress theme directory. Don t know how long it will need for them to make it available.

@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.

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.

simple reason why Andy could not turn BP as a seperate project… he did the opposite this year… he had a deal with Automattic…

why people always think that their way of doing things is always the best one… WordPress have no dogma… or it would be dead for years. when i started on this project, 8 years ago, i was with other projects with more straight dogmas… they usually die because of the narrowed thinking. WP is was larger than from a single entity…

Only registered users 2

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

Not specific for BP but works for BP also.

Great to have until the Privacy Module from Jeff S hits the road.

Maybe you could get it to work with two plugins:

First, install the auto-join-groups, but beware, I think it is still the old version (1.0) in https://wordpress.org/extend/plugins/auto-join-groups/ and not the new one (1.1) which you can find here: http://brentandmary.net/2009/10/24/bn-auto-join-group-plugin/ I have tested it with BP 1.2 and WPMU 2.9.1.1 and it works. (It also works on WPMU 2.8.4 with BP 1.1.2)

You need to create groups that match your profile fields, wheter it is interests or location. Only ‘selectbox’ and ‘textbox’ type profile fields are supported. The plugin work backwards so all existing users will be connected to their corresponding group. Neat.

Then, I imagine, you can try some of the plugins that will email group members about updates.