@Gpo1
Eventually I want to support hundreds of sites, the only constraint is time. I have added yours to my list of possible sites to support. Right now I am ranking requests based on Alexa rankings. I can guarantee that sites with a very small reach (like twitgoo with a tiny 0.031 reach) will be in some sort of pro pack.
I am not sure what you mean by “remote submit for gallery2 & 3 photos”
now i reinstalled everything and errors disappeard … bud sadly there’s a new one :
Fatal error: Call to undefined function bp_page_title() in /home/httpd/vhosts/idotter.ch/httpdocs/buddypress/wp-content/themes/bp-sn-parent/header.php on line 9
@MrMaz also advanced features like remote submit for gallery2 & 3 photos …
@MrMaz, Can you look into my request above ?
@andy
Thanks for taking the time to post some ideas about monetizing. I have been looking into all of those angles, except the documentation one is new, thank you.
I am definitely going to do paid support with a forum, and probably going to sell a “pro pack” that is loaded with advanced features like remote submit (reddit, digg), ad support, rich media pack, theme pack, etc.
The only site I have found that lets me get up and running quickly is wpplugins.com. I would rather do it all in house, but do not want to spend too much time dealing with all of the support software and payment solutions.
If anyone knows of other sites like wpplugins.com, please lmk!
Another idea would be to release support for alternate services for paid supporters, then once you receive enough donations, release it in the wild.
@mrmaz Why not start up premium support by means of a forum? Or perhaps offer more advanced tutorials or docs for paying supporters. Quite a few people have found this to be a successful model, and it doesn’t shut everyone out – reducing overal interest.
@MrMaz,
I willing to buy the pro version if you could add ustream.tv (aka youtube,but better ! ), twitpic ,twitgoo.com feeds .
Trunk is the work-in-progress version. If you find a bug with it, it’s best to report it on http://trac.buddypress.org.
@r-a-y that’s a different issue which relates to non-latin characters in URLs and BuddyPress slugs
@r-a-y:
I have resolve this problem.But Chinese displays ??? in buddypress rss url
co.jiaju99.com/members/yijia/activity/feed
Why?
I hear you. I just know I won’t have the time for this level of upgrading. I’m hoping I can disengage the Buddypress functionality from the BP template files (as should be the case for any true framework). Then, I could get full upgradeability of the theme framework (Hybrid) and just have to modify the BP functionality added via functions in the child.functions.php (based on functions available already from BP) and/or create custom BP templates myself.
I’m hoping that’s less work.
Someone ought to figure this WP framework vs. BP framework thing out. I’ll be checking out Ron’s work on Buddymatic and here he has one for Hybrid too.
Wow! I’m glad this topic got people thinking.
@Xevo, I do plan to use Hybrid (not thesis) and add the BP functionality, but not sure the implications as BP adds functionality with new releases. Sounds prone to breakage on upgrades. Someone at Automattic should be thinking about this if Mike is right about the future use of BP, which I think he is.
@Mike Pratt, I agree 100% regarding BPs future and enjoyed your thoughts in the video from Wordcamp NY
@Bowe, I’ll have to think more about the P2 solution, but doesn’t it mean I have ~9 tables multiplying by the number groups. If so, I’m looking for a lighter solution.
“BuddyPress on a sub-blog not the root blog”
Curious and a bit off-topic, sorry boonika: Back in BP 1.1, when I tested and run BP on blog_id_2 e,g, http://members.mysite.com/ – when a member created a blog, the URL would come up like e.g. http://username.members.mysite.com/ instead of the URL I want i.e. http://username.mysite.com/ so it turned me off and made me restart development with BP in blog_id_1 to present … Doesn’t this hold true anymore in BP 1.2?
Thanks
As I said in previous post, it works. But I did find something ‘weird’ going on. After I added ‘Site Wide Activity’ widget to one of the sidebars I have noticed that links to users profiles don’t work properly. Actually, they do if your Buddypress is active on the main blog, which is not the case with our site. Other than that, everything works fine.
Burt adsit created a plugin called bp-contents for group and member taxonomy, but it was never updated for bp 1.1 or above. I updated the group features to work in bp 1.1.2, but if I were you I would wait for the Buddypress team to add taxonomy stuff to the core (this will be better supported than my hacked bp-contents).
Any way, I hope to have some code for you guys to test out by the end of the week 
PS, if any one here has experience finding security vulnerabilities, I’d like to get some other sets of eyes to make sure my plugin is completely secure.
I replied to your post on testbp.org:
http://testbp.org/members/erich73/activity/57291/
—
Jeff’s plugin isn’t ready for BP 1.2. He mentioned in his blog post (http://jeffsayre.com/2009/12/05/buddypress-privacy-component-released/) that he’s waiting for development to cease, or at least be stable enough, so he can begin adding compatibility for v1.2.
@bowe
Right now my plugin doesn’t distinguish between different types of groups. But maybe today I will add an option that will let you enable different features in private vs public groups. The buddypress guys are working on a taxonomy system for groups that gives you more options than just private public or hidden, but that maybe a ways off. Sounds like you only need two types of groups right now anyway.
There’s nothing that will prevent normal users from joining a group in the usual way. You can set it so that they can set the group as “identifying” (with the group name next to their name) or not.
@mercime
Seems like it shouldn’t have any conflicts with the privacy plugin, but I’ll have to try it out to be sure.
Sorry for bumping this old post, but life is evoluting…
Such a plugin exist now:
https://wordpress.org/extend/plugins/buddypress-group-documents/
Ah, I see. Was wondering whether that might have been it. Thanks Andy. Guess I should wait until the next BuddyPress release then. Thanks.
I’ve activated and deactivated BP in WPMU admin and had no problems with it. As stripedsquirrel listed above, to rephrase – “It’s very important to first deactivate any plugins that require BuddyPress to run before deactivating BuddyPress plugin. Otherwise, yeah, you will get white screen in frontend and backend.
As for upgrading, not to encourage any bad practices but just to share that I am in project development mode right now and I’ve upgrading both WPMU/BP from trunks almost every other day this December without deactivating any plugins and did not get white screen – except the upgrade to WPMU 2.9 beta 2 trunk when it added a commentmeta table for each blog in WPMU install and run mysite.com/wp-admin/upgrade.php . Solution: Running mysite.com/wp-admin/wpmu-upgrade-site.php gave me back my frontend and backend.
Speaking of your Achievements plugin, do you plan on offering an update that allows us to make new achievements without editing the source code?
Feel free to email me back if it helps.
There is also a solution for that.. It’s called Community blogs: https://wordpress.org/extend/plugins/bp-community-blogs/
From the plugin description:
By activating the Community Blogs plugin, Administrators can give immediate registered user status to any member of their BuddyPress enabled site on the blogs they choose. All the member has to do is visit the blog. The user is silently added as a registered user of that blog. Administrators can choose the role the new user has. Either Contributor or Author. Admins can give access to all users or users from specific BuddyPress groups.
As soon as a (registered) users visit the Blog (in your case Community Voice page) it automatically gets added as an author and is allowed to post! Great huh? 
Currently the BP upgrade instructions mention this as step 3:
“Upgrading with the Plugin Updater
1. BACK UP your existing install including the database.
2. It’s very important to first de-activate any plugins that require BuddyPress to run before updating BuddyPress.
3. De-activate the BuddyPress plugin.”
https://codex.buddypress.org/getting-started/upgrading-from-10x/
This might need to be changed then? I actually would not know to what as I never managed to have a straight update without white-screens and other problems as described above, but maybe that was because of following the instructions?
Bowe,
Thanks, I also appreciated your suggestion about using P2 as a means of communicating to the group.
The community we are trying to create are not necessarily bloggers and we need an easy way for them to communicate site wide. For now I have created a group “Community Voice” to facilitate site wide communication, but a little clunky requiring everyone to join this group. Any thoughts would be greatly appreciated.
Bri@n
