Active
Project:
OG Project
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 May 2007 at 23:24 UTC
Updated:
4 Nov 2010 at 19:56 UTC
Jump to comment: Most recent file
looks like adding a .info file isn't all that was required to port this to 5.x core + OG. ;) the elements show up on the followup form, but they're not being saved when you submit the follow-up. seems as though i must dig deeply into the 5.x OG code and get this working again...
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 140951_update_project_update_og.patch | 888 bytes | greggles |
Comments
Comment #1
gregglesConfirmed. From reading the code it looks like one of the goals of this module was to prevent issues from losing their group affiliation. I'm not 100% certain, but a quick test of that aspect (as uid 1) seemed to show that a private issue inside of a group stays private from people outside the group after posting a comment.
So...the "only" piece to worry about is this changing the audience form.
Comment #2
gregglesChanging from public<->private seems like a new feature to me. I don't really see code related to it in the current module.
For my needs and I think a reasonable assumption for the module, groups and projects are tied heavily 1-1.
The attached patch fixes this problem for that 1-1 use case.
Comment #3
gregglesActually, the patch I posted is totally wrong for this issue :)
It should be posted over on #173639: Project nodes as OG: keeping project* content associated with both project and group.
Comment #4
dwwBased on #962446: 1-1 requirement (for now) this is more of a feature request than a bug. It might actually be better handled via #962554: Support for Organic Group in fact...