I'm going to be taking another look at this module, and working on removing the hard dependency on og_forum. IMHO og2list should be able to process incoming mail as whatever node type an admin wants. For many og use-cases (e.g. groups.drupal.org), taxonomy is not what's used to contain general group discussion.

We wouldn't want to lose the og_forum functionality if present, but we would want to let new incoming posts function as story nodes, for instance.

Comments

moshe weitzman’s picture

moshe weitzman commented

note that forum.module can hold any node type in D6 so this makes good sense anyway. thx.

damien_vancouver’s picture

damien_vancouver commented

I totally agree, it should do any node type. Users have asked for it in our deployment.

Commenting to any node type works already - as long as og2list sends the notifications.

You'd just need to have an admin setting to choose which content type and have the hook_nodeapi $op=insert branch handle it properly in og2list (ie wthout forum/taxonomy stuff, but using taxonomy if the admin did select a forum type). I'm not too familiar with how that part actually works in detail but I imagine it can't be too hard.

Also I've had really bad luck trying to get the new og_forum to work - we tried to use it and there were heinous SQL cross products happening and bringing the server to its knees. (when the og2list dust settles I plan to revisit this but yeah - no dependency on og_forum would be great, as we are now stuck at the old 5.x-1.x verison).