Difference between revisions of "Subform Requirements"
From ARK
Andydufton (talk | contribs) |
Andydufton (talk | contribs) |
||
Line 6: | Line 6: | ||
*'''sf_html_id''' - the form id tag (must be unique) | *'''sf_html_id''' - the form id tag (must be unique) | ||
*'''script''' - the script to use on this subform | *'''script''' - the script to use on this subform | ||
+ | |||
+ | It is important when creating subforms to also insert the corresponding markup into ARK (the sf_title). This can be accomplished using the [[Markup Administrator]]. | ||
====Example==== | ====Example==== |
Revision as of 13:11, 14 November 2008
All subforms have a number of required settings. A list of the current required settings for subforms follows:
- view_state - the default view state (min or max)
- edit_state - the default edit state (edit or entry or view)
- sf_nav_type - how to display the navigation in the subform (full, name or none)
- sf_title - this is the nickname of markup to display in the title bar of the sf
- sf_html_id - the form id tag (must be unique)
- script - the script to use on this subform
It is important when creating subforms to also insert the corresponding markup into ARK (the sf_title). This can be accomplished using the Markup Administrator.
Example
'view_state' => 'max', 'edit_state' => 'edit', 'sf_nav_type' => 'none', 'sf_title' => 'projection', //appears in the titlebar of the subform (mk nname) 'sf_html_id' => 'fst_cd_projection', //the form id tag (must be unique) 'script' => 'php/mod_fst/subforms/monument.php',