BuddyPress.org

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.

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

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/

Hi. This should work:

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

Now works. Welcome to testing:

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.

Thanks Tore !

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

Hi!

Thanks for the suggestion. I’ve been using a header-hack to ensure that no non-registrees are allowed into the website. I’ve only found https://wordpress.org/extend/plugins/registered-users-only-2/ that’s secure enough for me (all parts of the website). But it isn’t supporting BP 1.2. right now. I’m hoping for a release soon enough although.