BuddyPress.org

I’d like to comment for anyone who comes across this thread, if you do this just to get into the bbpress admin panel, *none* of the changes will carry across into BuddyPress -> Groups -> Forums views. You have to run an external bbPress installation for that to happen.

Copied the file as you recommended and still can’t find an admin panel for bbpress. Where do I go after copying the file?

Also, I took the bb-config.php file from the root, but there’s bb-config-sample.php in /wp-content/plugins/buddypress/bp-forums/bbpress/ are those the same?

Anyway…where’s the bbpress admin panel?

Best,

Dainis

PS: Is it because I installed buddypress first and then used the one click thing to install bbpress? I really don’t feel like wiping everything out and starting over just to re-order the installs…

You’d probably be better off downloading the latest trunk version and overwriting all BuddyPress files.

Before you overwrite though, deactivate BuddyPress.

OK, to bring the thread back to the original subject, in the current version of my site I use Burt Adsit’s solution for the most immediate privacy problem, making members sections members-only:

function js_restrict_access(){

global $bp, $bp_unfiltered_uri;



if (!is_user_logged_in() &&

(BP_MEMBERS_SLUG == $bp_unfiltered_uri[0] ||

BP_GROUPS_SLUG == $bp->current_component ||

BP_BLOGS_SLUG == $bp->current_component)){



bp_core_redirect( get_option('home') . "/register" );



}

}

add_action( 'wp', 'js_restrict_access', 3 );

Put that in bp-custom.php and it works pretty painlessly. It doesn’t have a built-in message to let the user know why he’s being redirected though.

Haven’t tried Jeff Sayre solution yet, but apparently it has some problems. I’ll try that one in my next upgrade to BP 1.2 and WP 3.0.

Also commercial membership plugins apparently have built-in privacy features, so that could be a solution. Haven’t gotten that far yet…

@dcartwright

Non-admin page creation works great! This is super simple an will encourage people to be more active! Small detail but great impact! I would suggest to move the create a wiki page box to the top.

Since there is a Group Wiki Directory Table that shows all pages, what is the benefit of having all pages listed on top? It looks kind of clunky and confusing?

I did a little mockup to clarify what i mean: http://i47.tinypic.com/15r0di0.png

By the way the Group Wiki Directory Table seems to be a good starting point for a global Wiki Directory Page.

Great work! This plugin will become super useful especially if you use buddypress for students! Great first RC!

EDIT: I just looked at the mockup and saw that i added vertical-align: top instead of middle. Just if someone is wondering.

EDIT 2: @David: I can understand the benefit of showing all buttons on the editor, but i also know how confusing all these buttons are for avarage users. It’s easier for a tech user to press a button for advanced options instead of confusing avarage users with to many buttons. But sure, thats personal taste.

@auturo Since I see you and others are posting some new questions in the forum about bbpress integration. perhaps ya’ll should follow Boones’ lead on it regarding (whether to maintain an external installation of bbPress or migrate over). https://buddypress.org/forums/topic/bbpress-integration-after-bp-upgrade I believe the groundwork for what you need to know is here.

You’ll need to add a bb-config.php file to the bp-forums directory in order to access it. You can take a look at this thread.

@Peterverkooijen

hi Peter

We understand you pointing to the issues. There is no problem with that. It is a community project and Automattic and Andy is doing the good things for us. Automattic does not get funds for supporting wp+wpmu+bp(well Now they may get as WordPress foundation has been formed).

Instead of criticizing, if we appreciate what they have done for us and politely ask for the features, I am sure, Andy is listening and will be glad to accomodate.

Buddypress is one of the great project and see how much improvement has been in recent times. Please do not take the things personal, and let us keep the community constructive, It will be better for all of us.

Hope you don’t mind my words. Yes, currently Bp is more developer friendly than the end user, but with time, It has improved so much and you may expect it to be much more end user friendly by bp 1.3(my guess)

Please let us keep it constructive.

@all, Please keep this thread free from personal attacks before DjPaul sees this thread

https://trac.buddypress.org/changeset/2448

If you are comparing an open source project to a car manufacturer then you don’t get it. Did you pay for BuddyPress?

Automattic is a regular company. WP is supposedly aimed at content creators, not developers. If WP/WPMU/BP lacks certain key functionality that forces users to get into coding, it fails in its mission. As a user I’m free to point that out without having to pay tribute to the developers first. I didn’t pay for WP/BP, but don’t have any obligations towards Automattic either.

@Erich73, I didn’t start turning this thread into an attack on me.

@Peterverkooijen

If you are comparing an open source project to a car manufacturer then you don’t get it. Did you pay for BuddyPress? Andy is right, you sound like a troll. You should word your posts to sound more constructive and stop taking shots at the developers.

There are many ways to contribute besides writing code. You can write documentation, help organize developers, write specs for plugins/features and put together a team of people to make it happen.

There’s no need to worry about privacy features in BuddyPress. As I have stated previously on these forums and on my blog, I am committed to bringing my current Privacy Component up to code to work with BP 1.2. With the 1.2-beta coming out very soon, I plan to use that to finalize the new privacy codebase.

As it has been discussed before, it will be up to the community to decide the fate of my BP privacy solution. If it is deemed sufficiently useful, valuable, and robust, it will be considered for eventual inclusion into the core.

But, I’ll stress once more, that this is not my decision. Going forward, I fully expect some form of privacy to make it into core down the road—whether it is my code, part of my code, or new code.

well, this should help you. You need the privacy component.

Check out Jeff’s privacy component here

http://jeffsayre.com/2009/12/05/buddypress-privacy-component-released/

Did you create a child theme? If you did, then you should have no problems. It looks to me like you do not have any of the javascript, which means nothing is loading properly.

You should be doing this:

https://buddypress.org/forums/topic/child-themes-12-bp-default#post-34501

@MrMaz

Updating the “LINKS” directory in my theme worked!

But now, the detected IMAGE for the thumbnail doesnt actually get used when I save the link.

any thoughts?

— im curious.. when it dynamically detects the thumbnail to use.. where does it store the data?

P.S. I apologize for the delayed response .. I got really really sick the past few days.

There was some talk in the recent buddypress-dev meeting about creating a poll for future feature requests. When such a poll appears on the site, be sure to vote for privacy in the core if you think it’s important for it not to be located in a plugin.

Didn’t we do the exact same thing six months ago?

Privacy is crucial imho. If access management is not core, what is? Social networks can’t function without privacy controls. Members won’t use it for anything serious if they can’t control whether their posts goes to their friends or out to the world.

I hadn’t paid much attention to this issue because I assumed it was coming. With all due respect, the developers seem more interested in “new features” and cool coding challenges than straightforward usability and making sure the core is rock solid.

@andrea_r i was wondering this. that is BRILL.

It’s true that the roadmap has changed a lot: https://buddypress.org/about/roadmap/

There was some talk in the recent buddypress-dev meeting about creating a poll for future feature requests. When such a poll appears on the site, be sure to vote for privacy in the core if you think it’s important for it not to be located in a plugin.

BuddyPress’s standard “forums” links are created with the assumption that BP is using the standard integrated version of bbPress. Since your installation is elsewhere, you’ll have to redirect those links. It should only be in one place:

In header.php of your BP theme, replace <a href="<?php echo get_option('home') ?>/<?php echo BP_FORUMS_SLUG ?>" title="<?php _e( 'Forums', 'buddypress' ) ?>"><?php _e( 'Forums', 'buddypress' ) ?></a> with <a href="http://www.australianracinggreyhound.com/forums/" title="<?php _e( 'Forums', 'buddypress' ) ?>"><?php _e( 'Forums', 'buddypress' ) ?></a>

As for your more general question, I faced the same issue with a project of mine (whether to maintain an external installation of bbPress or migrate over). I decided that, in the long run, it would be best to move to the standard, integrated version of bbPress. I described the process here: http://teleogistic.net/2009/12/upgrading-from-buddypress-1-0-to-1-1/

Not sure what’s causing your login issue, but it might be fixable by hardcoding the link into your theme’s header.php file. Replace <?php echo site_url( 'wp-login.php' ) ?> with the correct path to the login page.