Search Results for 'buddypress'
-
Search Results
-
BuddyPress.org is the insider community. If you’re registered and paying attention, then you’re one of the cool kids.
There’s a few reasons why BuddyPress.org works and looks different than a usual BuddyPress installation does out of the box. I’ll do my best to explain them for you (and everyone else) but I can assure you, there’s nothing stopping anyone from mimicking this or infinite other kinds of hybrid installations.
1. This site uses the old and very yucky deep integration method with bbPress. Before BuddyPress 1.1 that was the only way to do it. With 1.1 Andy wrote an abstraction layer for bbPress to seamlessly bring its functionality into a WordPress installation.
2. The decision was made that forums made the most sense when linked directly to a group of users. Rogue forum categories without a group of users to attach them to, have taken a back seat for the time being. This has been the topic of debate for a while, but it won’t change for 1.2 and probably won’t change until bbPress as a whole gets a little more attention.
2. Because BuddyPress.org links directly with WordPress user and usermeta tables (which is why your 1 login works at all WP related sites), upgrading and shifting around over a million registered users isn’t a task to be taken lightly.
3. Since Buddypress 1.1 was released, BuddyPress.org hasn’t changed a single bit. Little to no attention has been paid to the inner workings of this site, and all efforts have been poured into the project itself in a very successful attempt to deliver a much more stable and solid project. Even group avatars on this site are still broken from the conversion.
4. The purpose of the support forums is to have a central community devoted to the questions and answers that a wide array of users have while installing, theme-ing, and in general just using BuddyPress. If you have needs that don’t fall within the core code then you’re stepping outside of core support and looking for custom development.
5. Many people on the forums (including myself) have stepped up and taken on side projects (pro bono or as paid clients.) A slew of plugins are available specifically to enhance parts of BuddyPress, but just like with WordPress if nothing currently exists that does what you need, you either need do it yourself or find someone to do it for you in a way that fits your budget.
6. BuddyPress 1.0 launched in April of 2009. It’s less than a year old and 2 major updates have already come through with even more to come in 2010. It’s still a baby compared to WordPress and bbPress, and I think Andy and myself will be the first people to say that it’s still capable of a lot more. Patches are always welcome, and in the past year the number of code committers has doubled (from 1 to 2
) and the number of significantly contributing code patchers, bug reports, and trac tickets has just about doubled also. So, if you’re unhappy, I can understand why. In a way BuddyPress.org sets an unrealistic expectation of a turn-key installation. If you feel you’ve been mislead in one way or another, that makes sense to me. Your opinion is valid, and when the site is updated to 1.2, I think you’ll be pleased.
In the meantime, if you choose not to use it that’s okay. If you choose to study the code and start submitting ideas and patches, that’s cool too. Whatever anyone decides to do, I don’t think anyone will be mad. We’re all buddies here, remember?
Dude – You’ve been watching too many conspiracy theory movies lately. Let me try and put some of your questions to rest:
1. There is no group of insiders. Just folks who have been around since Andy started putting code in the repository. There is no conspiracy for those “in the know” to get guys like you to pay for stuff. We’re all here on our own dime. Some make money in WP/BP related endeavors but they are still here on these forums because it validates their skill set and they’re also good people.
2. You need to hang out at http://testbp.org for awhile. It is what you get “out of the box” in BP. I don’t want to be to snarky here, but that fact is written all over the place. Not sure how you don’t know that. The theme at buddypress.org is (aside from being pretty outdated as far as BP goes) Andy’s own creation. He has not once said it is what you get with BP nor has he intimated that it would be available. Way back when, we asked him to make it available with no luck. O well, no big deal. You seem to think it’s his fault for not giving it to you? FYI, buddypress.org is not a typical BP install. Groups are barely used. Why do you have it in your head that it is?
3. No matter how much nice language you use, calling this community “two-faced” is not only a sure-fire way to make enemies but it’s a total falsehood. In fact, it’s an insult to all the volunteers who put in countless hours answering questions of people to lazy to read all the good info at their finger tips who’d rather just rehash the same basic stuff over and over. It’s a miracle we still get their awesome help.
SO here’s a few suggestions: Quit masking your contempt for this community in polite prose. Fill out your profile with links and such so you are more than just a username throwing barbs. Read the codex and all the great documentation and to what DJPaul, jjj and all the other selfless BP-asisters tell you.. Perhaps a thread like “I’m trying to replicate the forum functionality the way Andy does it here on bp.org, does anyone know how that’s done” might be way to start.
Good luck to you. We’re always here to help
ahh alright, you are either missing the one or the other. hmm.. I think, I should have pasted both the piece of code together.
Well, here it goes, and I hope, this must work
add_filter("bp_page_title", "bpdev_blog_title",10,2);
function bpdev_blog_title($complete_title,$title_old)
{//hack page title for single article
global $bp,$current_blog,$post;
if ( bp_is_blog_page() ){
if ( is_single() ){
$title = __( $post->post_title, 'buddypress' );
if ( defined( 'BP_ENABLE_MULTIBLOG' ) ) {
$blog_title = get_blog_option( $current_blog->blog_id, 'blogname' );
} else {
$blog_title = get_blog_option( BP_ROOT_BLOG, 'blogname' );
}
return $blog_title . ' | ' . esc_attr( $title );
}
}
return $complete_title;
}Please use the complete code and put it into your bp-custom.php. let me know If it still does not work.
Both Gallery2 integrations and Lifestream are, from experience of an user hosted on a clustered server, resource hogs. The existing Gallery2 integration plugin, WPG2, is according to what I know, an orphaned project.
I have to disable WP-cron on Mondays and Tuesdays because LifeStream goes crazy and it also bugs me that its javascript is still in the header. I can’t even imagine what would happen if my site’s users, in a future BP community, were syndicating contents together.
Of course, I respect the developer a lot and I understand that he cannot get everything done at once (and that it is likely the reason there has not been Lifestream 1.0 yet), I am just sharing my experience so nobody else gets “hurt” if they’re hosted with one of the companies that does not tolerate short-term high load peaks.
Absolutely! I’m using it for an accordion widget in my soon to be released theme. I’ve also written a tutorial for creating a TOOLs powered welcome slider:
http://www.bp-tricks.com/design/creating-a-jquery-welcome-slider-for-your-buddypress-homepage/
It works great, causes no conflicts and it’s very lightweight. Be sure to include the js at the top your header btw, because other JS scripts might cause conflicts if they are loaded first.
If you make anything cool with it let me know
