BuddyPress.org

Take a look at this.

I really don’t recommend building in a php framework into a existing cms, it could cause a lot of issues.

1. A buddypress theme isn’t so different from a standard wordpress theme, it just has a few extras.

2. Not sure what you mean by this, you have to install bp on wpmu, you can’t install them seperately. Bp is a plugin for wpmu.

3. Once installed bp correctly on wpmu or just wp, you get profiles, activities, groups etc.

Do you really understand what wpmu is? Basically its standard wordpress, but allows you or your users to make multiple blogs on one wordpress install. Buddypress allows you to turn your main blog into a social community, by adding profile and frieding options and the earlier named options.

@osasko, do you use the email login plugin? You can’t get rid of the username entirely, because WordPress is built around it, but you can autogenerate a username and hide the input field on register.php by adding type=”hidden”. It’s an ugly hack…

So I was having the problem with this on the single blog version of wordpress but not the multi user version on the same server. Then on the same server I created a brand new install of wordpress and buddypress and got it working there. I eventually found that the upload path that worked had /var/www/vhosts/url/httpdocs/wp-content/uploads but the one that did not work had just wp-content/uploads. once i changed this everything worked.

Jump in already. I’m not a programmer and the water is fine. Although BP’s Codex is a work in progress, things work the same as in wordpress which has a detailed (if disorganized) Codex. Learning Loops, hooks and php functions is enough to get started. Pick up Ajax/Jquery later.

I bought some books to help me, but you may not need them. There’s a BP book coming soon, which should help. You could probably develop something quickly, but it’ll take some time to understand how it actually works.

Here’s a tutorial for setting up XAMPP and WordPress:

http://sixrevisions.com/tutorials/web-development-tutorials/using-xampp-for-local-wordpress-theme-development/

If you’re not planning on using member blogs, this tutorial should get you up and running with WordPress. Then all you need to do is install BuddyPress.

Simple plugins that leverage established, mature gallery apps would prevent much of those upgrade dilemmas. Let Zenphoto and NextGen handle upload, compression, database storage, gallery creation, etc. The BP plugins then only have to provide ways to display images stored by those apps within the BP context.

That is the open source approach. What Djsteve suggests is the proprietary commercial software approach. Nothing wrong with that, but Boonex and SocialEngine are already doing that. If that’s what you want, expect to pay.

Personally I chose WP/BP because I want to be able to mix and mash scripts. Built-in forums, galleries, event management, etc. only make that harder.

When you upgrade to BP 1.2, you can use the BP backwards compatibility plugin:

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

That will probably be the easiest way to keep your template tags.

Read this blog post:

https://buddypress.org/blog/news/buddypress-1-2-beta/

Also what are these “errors” you speak of? Is it theme-related? Is it plugin-related?

Are you installing BP 1.2 beta on WPMU or standard WordPress?

When I have issues like this I open Firebug for Firefox and I can usually track down the problem.

Just change the upload path setting and filter the location, not a big deal.

Tutorial for creating BuddyPress Child Theme – https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

Use Google for more info re creating WordPress Child Themes

BuddyPress Codex – https://codex.buddypress.org/

BuddyPress Components/Features – https://buddypress.org/about/

Examples of BuddyPress sites and usage – https://wordpress.org/showcase/flavor/buddypress/

In child theme’s style.css, add BuddyPress tag ala bp-classic’s style.css where at top you see

Tags: buddypress, three-columns, white, orange

I agree that privacy is a prime concern, but I think by using plugins that work to your needs is a better approach then making everything core..

To use your analogy, WordPress is an Engine in a car.. Tested to be working 100% and made sure everything is perfect…

BuddyPress is an aftermarket Turbo that a bunch of guys got working on that engine..

It’s awesome, we all want it, but its not going to be totally perfect out the gate, and in the end may make your engine blow up..

Over Time I see privacy, images, user levels, events, projects, etc. becoming core but for now the idea is a stable base we can add on to..

If anyone ever used WP 1+ the switch to 2+ was NUTS and then 2.5+ OMG..

So much of what was a “Plugin” became core, and now look at 2.9 All those image plugins, thumbnail plugins, ETC went out the window when the core worked that functionality in.

@Andy

Thanks. I can probably figure out what you meant by this last post. I’ll look for a buddypress tag in the css header of the parent/child. I agree this will probably never be ideal as anytime there is a struggle between two ‘parents.’ Code mirroring life.