posting new nodes into organic groups (needs generic solution)
| Project: | Subscribe |
| Version: | HEAD |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
i have a client requirement where nodes posted to one organic group need to pub/sub into a corresponding group at the remote site. i know what to do on the publish side (let views.module create node lists for publishing), but the subscribe side is fuzzy. i clearly need a mapping between remote og and local og. but even with that, where in the receiving process should this check be made, and how do we let 3rd party modules like og participate in the process.
my proposal:
- let 3rd party modules maintain own mappings and add those mapping as new tabs on the publish admin page
- right before node_save() is called in subscribe_import(), call nodeapi('submit'). this triggers og to preoare the node for saving. og will recognize that this node is being submitted via subscription (we need a marker like this in $node), and then to the lookup to the map and then setup $node as needed. then node_save() does its thing and all is well. anyone know of repurcussions to calling nodeapi('submit') like this? if so, i guess we could call nodeapi('subscribe_submit') instead.
feedback welcome.

#1
I was thinking we'd use either a new _import hook or a nodeapi 'import' op.