Standalone versus embedded action set (organic group) submissions
Important differences:
The differene already noted in the #node comparison-- no node author name.
$form['#node']->name = 'Username'
And the same username difference, but in a different place:
$form['author']['name']['#default_value'] = 'Username'
blank in embedded
standalone:
$form[#action] => /eng/node/add/action-group
embedded:
$form[#action] => /eng/node/add/action
standalone (embedded subform has NO token information):
$form[#token] => action_group_node_form
$form[form_token] => Array
(
[#id] => edit-action-group-node-form-form-token
[#type] => token
[#default_value] => 056e9c6385230555165d2561fa43755f
)
embedded (standalone has no process or pre-render):
$form[#process] => Array
(
[subform_element_separate_data_prepare] => Array
(
)
)
$form[#pre_render] => Array
(
[0] => subform_element_separate_data
)
I think that's it, aside from time differences which don't count. Agaric used FileMerge.app, which is pretty much a wrapper around GNUnix diff.
Resolution
More like this
- Action set organic group as passed through subform versus standalone
- Allow users to assign issues to other people in the project group (organic groups and project module integration)
- Adding and modifying organic group action (create content) links
- Do not show group-adding subform when adding an action to an existing group
- Linked to from group versus unlinked node creation


Comments
Post new comment