og

I committed new code to OG today and rolled it to this site. We are now capable of completely private groups. Although we always have supported private content in a group, the group homepage has always been public. Thats not so anymore. A group can choose to be private now. I don't expect much use for that here, except for private planning groups like Drupalcon, Google Summer of code mentors, and so on.

Please let me know if you see funny behavior related to posting content or creating groups.

Currently, within OG, all the group settings are set sitewide for all types of group nodes. We are looking to implement group type by group type default permissions to allow for different types of groups within the same site --

We will be working out a solution to this issue and releasing the code back as a contrib module -- however, before we start coding we want to get some feedback/see if anyone else was thinking along similar lines.

The issue is here: http://drupal.org/node/192933 -- please centralize any discussion on the issue queue.

Cheers,

Bill

Buenos días a todos.

Quiero colaborar con la traducción del módulo OG, pero no encontré cómo hacerlo en Drupal. Es decir, hice traducciones antes, conozco la traducción, el gettext, los .po, etc.; lo que no sé es cómo integrar esto a la distribución del módulo OG.

¿Alguien alguna vez lo hizo y/o sabe apuntarme a algún/os punteros para comenzar?

Gracias y saludos...

--
EM

Hello,
I'm here because it seems like the only place I am likely to find some help with Access Control, having scoured the internet for help elsewhere...

Hi Glad to find a churches group on here,

I just wanted to introduce myself and introduce a project I am working on. well I am Craig Bertrand...and this is the project...

We (The Missions Organization I work with) are starting a Christian Collaboration Community that will have the option to host civicrm for churches and other Christian groups and we will be trying to make civicrm "just work" for churches. We figure this solution should work for churches with no techie folks, or for those who just dont want to worry about maintaining a server and drupal/civicrm core.

An admin in my group gets access denied. Ideally, group admins should be able to send email?

The Gradebook and OG_Gradebook modules have FINALLY been ported to Drupal 5. They are still marked development and need massive of testing. Please feel free to try it out and submit bugs and features requests.

Has anyone successfully implemented og where each group lives on its own subdomain, but on a shared code base? We are looking at this as an alternative to a multi-site (separarate dbs w/ shared users) implementation. The wrinkle on this project is that the site could grow to a couple hundred subdomains. They don't need to be added on-the-fly via admin interface.

Any suggested approaches to this?

Is there a roadmap anyone might suggest for feature enhancements or supporting module development we might consider for the og module package itself?

(If 5.0 beta proceeds well, we'll likely be wanting to build this in 5.0 as well.)

I'm pretty excited that I finally deployed the og_vocab module on this site. This enables each group to maintain its own classification system for its posts. It also offers a handy block called 'Group categories' which helps subscribers navigate by taxonomy term.

You can see the block on the right hand side of any group page if that group has actually created and used a group specific vocabulary. Also, notice that the display of terms at bottom of each post is now grouped by vocabulary. For an example of both of these changes, see http://groups.drupal.org/node/192.

In order to create a group specific vocabulary, you must be an admin of a group or a sitewide editor. If you qualify, you will see a new categories tab on the group home page which helps add/edit.

Okay, I just removed my previous post. I'm not sure what I was thinking, but I think everyone here can post full stories when they have something interesting. Bah. ;)

Anyway, I did want to make a post about the management aspect of running a church web site. This isn't particularly related to og or even Drupal, but I did want to make a few comments since I've been the volunteer webmaster of our church for three years.