Closed (fixed)
Project:
OG Audience
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
24 Mar 2007 at 20:28 UTC
Updated:
26 Apr 2007 at 02:30 UTC
Jump to comment: Most recent file
Hi there,
This module looks really useful for a collaborative website! IS there any chance there could be a version for drupal 5! Is this still under developpement and maintaining?
Thanks
Patchak
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 5x_up_og_audience_1.patch | 16.91 KB | pwolanin |
Comments
Comment #1
David Lesieur commentedPatches to port this module to Drupal 5 are welcome!
Comment #2
pwolanin commentedpatchak has arranged for me to update this module to 5.x. Can I have CVS access? Otherwise, can you branch for 4.7 so that a patch for 5.x can be applied to HEAD?
Here's my basic plan for using the API:
- we don't want to call node_save() to make these updates, or directly mess with the {node_access} table.
- for the node access system part, we can use the node_access_acquire_grants() function to update the node access table.
- for the og part of this, we will use the og API function og_save_ancestry() to get og to update its tables.
Comment #3
pwolanin commentedDigging into the code- one observation: the current code only allows re-assignment if the node already belongs to a group. I guess there is no good way to set the "Public" setting if it's not already part of a group?
Comment #4
pwolanin commentedAttached patch updates the module for 5.x. I think it's RTBC, based on my testing. Note new settings page and black, as well as updated REAME.
Comment #5
David Lesieur commentedUnfortunately, I won't be able to do a proper review right now, but you now have cvs access, feel free to use it. :-) Thanks for this work, and sorry for the lack of feedback so far!
Comment #6
pwolanin commentedOk, no problem. The API calls might be useful if you need to update OG Public Access.
Comment #7
pwolanin commentedComment #8
(not verified) commented