Difference between revisions of "Sf modtype"
From ARK
(→Example Configuration) |
|||
| Line 21: | Line 21: | ||
'op_label' => 'space', | 'op_label' => 'space', | ||
'op_input' => 'save', | 'op_input' => 'save', | ||
| − | 'op_modtype' => FALSE, // | + | 'op_modtype' => FALSE, //this is FALSE as should not be set to different fields |
'conflict_res_sf' => 'conf_mcd_modtype_conflicts', | 'conflict_res_sf' => 'conf_mcd_modtype_conflicts', | ||
'fields' => | 'fields' => | ||
Latest revision as of 09:20, 26 June 2013
Description
This subform displays and edits the modtype of an item. It can be used either as a standard subform or within an overlay.
Edits are complex and require a user feedback and checking routine that uses conflict resolution.
Additional Fields
- conflict_res_sf - this is used to specify the subform conf to use when conflict resolution information is needed to be be passed to the user. This is most likely to use sf_modtype_conflicts.php.
Example Configuration
An example of sf_modtype in action
$conf_mcd_modtype =
array(
'view_state' => 'max',
'edit_state' => 'view',
'sf_nav_type' => 'full',
'sf_title' => 'cxttype',
'sf_html_id' => 'cxt_modtype', // Must be unique
'script' => 'php/subforms/sf_modtype.php',
'op_label' => 'space',
'op_input' => 'save',
'op_modtype' => FALSE, //this is FALSE as should not be set to different fields
'conflict_res_sf' => 'conf_mcd_modtype_conflicts',
'fields' =>
array(
$conf_field_cxttype
)
);