Difference between revisions of "Sf modtype"

From ARK
Jump to: navigation, search
(Additional Fields)
(Example Configuration)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
===Description===
 
===Description===
The data class 'modtype' will handle modules with different types (eg. the standard context module has types cut, fill, masonry, etc.).  The configuration of module types will be specific to each module.
+
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 [[Subform Conflict Resolution| conflict resolution]].  
  
 
===Additional Fields===
 
===Additional Fields===
*'''classtype''' - this is the module type, as found in the mod_lut (eg. cxt_lut_cxttype has classtype cxttype)
+
*'''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.
*'''alias_tbl''' - the alias table is cor_tbl_col, make sure there is an entry in cor_tbl_col for the relevant modtype and that you have added an associated [[Alias Administration|alias]]
 
*'''alias_src_key''' - the text entered in cor_tbl_col corresponding with the modtype (eg. cxttype, abktype, etc)
 
  
 
===Example Configuration===
 
===Example Configuration===
 +
An example of sf_modtype in action
 +
 
<pre>
 
<pre>
$conf_field_cxttype =
+
$conf_mcd_modtype =
 
     array(
 
     array(
         'dataclass' => 'modtype',
+
         'view_state' => 'max',
         'classtype' => 'cxttype',
+
         'edit_state' => 'view',
         'alias_tbl' => 'cor_tbl_col',
+
        'sf_nav_type' => 'full',
         'alias_col' => 'dbname',
+
         'sf_title' => 'cxttype',  
         'alias_src_key' => 'cxttype',
+
         'sf_html_id' => 'cxt_modtype', // Must be unique
         'alias_type' => '1',
+
         'script' => 'php/subforms/sf_modtype.php',
         'editable' => TRUE,
+
         'op_label' => 'space',
         'hidden' => FALSE,
+
         'op_input' => 'save',
'add_validation' => 'none',
+
         'op_modtype' => FALSE, //this is FALSE as should not be set to different fields
         'edt_validation' => 'none'
+
        'conflict_res_sf' => 'conf_mcd_modtype_conflicts',
 +
         'fields' =>
 +
            array(
 +
                $conf_field_cxttype
 +
        )
 
);
 
);
 
</pre>
 
</pre>
 +
 +
[[category:Administrator]]

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
        )
);