Well, one solution would be to have a blog created for the group with all group members set as editors.
The BuddyPress Codex (http://codex.buddypress.org) is run off WP and instead of a normal wiki users log in and are able to edit the pages – revisions are saved thanks to post/page revisions.
It would just need a plugin to add some options to the group admin area; Group Blog settings for example.
Thanks for the idea, but could you please elaborate a bit:
What does “a blog created for a group” actually mean? I can find no possibility to associate a blog with a specific group. Did I understand you correctly that the only way to do this would be to _manually_ add each group member as an editor to a basically arbitrary blog?
The missing plugin would then have to have a possibility to
-assign a blog to this group
-automagically activate present and future group members as editors in the given blog
-link to blog backend for writing posts and pages
There is a plugin by Burt called Community Groups, and this will help you do what hempsworth is describing (and what you are requesting) quite easily. Do a search for some of the topics I’ve posted in recently, and you’ll find it somewhere in there.
Otherwise you could just manually add each member of the group as a user/editor of the blog, which will provide you the same functionality but obviously be more tedious as members join and leave the group.
That was a very good tip, thank you.
Now I’ve got the Community Blogs plugin installed and activated.
I also created (with admin user) a new blog. However, when I log in with another user and visit the blog and then click on the “Site Admin” link to write a post, it takes me to the backend just fine but registers me as a user to the site’s main blog. That is also where the post goes, not the blog I visited (group blog).
Any ideas? Could this be due to the fact that I have my BP installation in a directory (i.e. mydomain.com/bpinstallation) and not in the root of my domain?
innoj, not sure what is going on. You have Community Blogs 0.4 installed. You’ve activated it on the blog that you want to be a group blog. (this is not an mu-plugins type thing) As a normal user who belongs to a group that you setup in the settings page, you visit the group blog. You are now a contributor/author.
“Site Admin” shouldn’t show at all if you are contributor/author.
Did some more testing:
-“Site Admin” link shows up always, but it leads to a dashboard view with only “Profile” and “Tools” on the menu. Seems about right to me.
-Community Blogs seems to work fine when I set “Allow All Registered Users” to Yes. Setting it to No and entering my group slug into the “Allow Access” field doesn’t seem to work.
Oh. “site admin”, you must be using Tarski theme or have the meta widget running in your theme. I thought you were talking about “site admin” in the mu backend.
Do you get an error msg saying “Invalid group slug: ‘your-group-slug'”?
Testing it again I see that nope it doesn’t work. I must have screwed up something in latest version. I’ll debug it and post a msg here. I have something to do for a couple of hours but I’ll get to it today. Thanks for the heads up. 
Suppose it would help to have a site with some traffic to have tested that. Sorry Burt. 
OK. Certainly not your fault John. Mine for being in too much of a hurry to get things working with RC-1 and not doing thorough testing.
Community Blogs v0.41 available:
http://code.ourcommoninterest.org/2009/01/02/community-and-group-blogs-in-a-can/
I added an action that can be trapped when a user is added or upgraded. For your time and trouble.
I guess I hadn’t put much thought to it, but the group forum icons don’t show up for guests, at least not for me they don’t. I haven’t looked at the code to see if this is intentional or simply being at the mercy of the core, but figured I’d mention it.
Completely forgot about this thread, but very glad I found it again! This is actually a feature I really wanted but didn’t think was possible.
The plugin looks great, will certainly test; thanks Burt!
The sort of functionality I was looking for was the following:
An admin of a group can go to the group settings page and select ‘Create Group Blog’, which would take them to a blog creation page.
They could set the name of the blog, they could set the privacy level (to appear in Google searches or not), and they could choose from the members of that group who would be set as contributor, editor or admin of the new blog, probably through radio buttons next to each group member.
Then, they could click ‘Create’, and the blog would be registered with the group members added and their relevant roles set.
An item in the groups sidebar, under ‘Forum, Wire’ etc, could be ‘Blog’, and would go to the designated blog for that group. We could even output their posts *within* the BuddyPress theme, either pulling from the RSS feed or directly from the DB, and have a ‘Visit the blog here’ link above the most recent posts.
Is this at all possible? I think it’s a much more user-friendly way for groups to set up team blogs.
John, intentional. My template shows the group avs for the groups I belong to. You can change it.
hempsworth, to be honest, this sounds more like a forum functionality than a blog to me. WordPress has never really had this type of straight forward user based permissions functionality, and while I can say that I think it sure could use it, I will also admit publically that I’m probably not the guy for the job. I think ideas like this should be added as feature requests to the trac, because they’re outside of the current 1.0 scope of BuddyPress, and would also involve some changes to WordPressMU.
Burt, I will take a gander. Also, you think possible to add an option to make the members of the group all editors? Could sort of have a blog/wiki that way.
@John, nothing prevents a blog having everyone as ‘editor’. I can just add a role to the default roles in the community blogs plugin.
@hempsworth, I’d like to see the same functionality you describe in bp for group blogs. I started it with the community blogs plugin. Haven’t gotten any further with it.
Sorry for the belated reply – we were in a bit of a pinch so we had to ditch BP alltogether and go with Drupal/Organic Groups this time. Not that that’s problem-free, but it’s a more complete package feature-wise for the project at hand.
Anyways, a thousand thanks to Burt for the updated version. I’ll give it a spin asap.
