Mod settings.php - Revision history

Jessogden: /* User Field Configuration */

2011-02-24T17:44:02Z

‎User Field Configuration

2011-02-24T17:43:29Z

‎User Field Configuration

2011-02-24T17:40:02Z

‎User Field Configuration

2011-02-24T17:39:33Z

‎Data View

2011-02-24T17:33:41Z

‎Data View

2011-02-24T17:26:06Z

‎Data View

2011-02-24T17:25:43Z

‎Data View

2011-02-24T17:24:11Z

‎Chat

2011-02-24T17:21:48Z

‎Delete and Edit Functions

2011-02-24T17:21:09Z

‎Delete and Edit Functions

@@ Line 291: / Line 291: @@
 As of v0.8 the user can add or remove fields to any of the views available on the data_view page. This is the sf_conf for the subform that is used to add/remove fields. The fields listed here are the fields that the admin wishes to make available to the user as options for adding to the view. Keeping the list short can help to make the user interface easier to understand.
 <br>
-Fields in this list MUST have field_id set up (correctly) in [[field_settings.php#Sorting]]
+Fields in this list MUST have field_id set up (correctly) in [[field_settings.php#Sorting|field_settings]]
 <pre>
 // Add fields to the current view subform

@@ Line 291: / Line 291: @@
 As of v0.8 the user can add or remove fields to any of the views available on the data_view page. This is the sf_conf for the subform that is used to add/remove fields. The fields listed here are the fields that the admin wishes to make available to the user as options for adding to the view. Keeping the list short can help to make the user interface easier to understand.
 <br>
-Fields in this list MUST have field_id set up (correctly) in [[field_settings.php#Common/Obligatory Attribute#Sorting]]
+Fields in this list MUST have field_id set up (correctly) in [[field_settings.php#Sorting]]
 <pre>
 // Add fields to the current view subform

@@ Line 291: / Line 291: @@
 As of v0.8 the user can add or remove fields to any of the views available on the data_view page. This is the sf_conf for the subform that is used to add/remove fields. The fields listed here are the fields that the admin wishes to make available to the user as options for adding to the view. Keeping the list short can help to make the user interface easier to understand.
 <br>
-Fields in this list MUST have field_id set up (correctly) in [[field_settings.php|Common/Obligatory Attribute#Sorting]]
+Fields in this list MUST have field_id set up (correctly) in [[field_settings.php#Common/Obligatory Attribute#Sorting]]
 <pre>
 // Add fields to the current view subform

@@ Line 291: / Line 291: @@
 As of v0.8 the user can add or remove fields to any of the views available on the data_view page. This is the sf_conf for the subform that is used to add/remove fields. The fields listed here are the fields that the admin wishes to make available to the user as options for adding to the view. Keeping the list short can help to make the user interface easier to understand.
 <br>
-Fields in this list MUST have field_id set up (correctly) in [[field_settings.php]]
+Fields in this list MUST have field_id set up (correctly) in [[field_settings.php|Common/Obligatory Attribute#Sorting]]
 <pre>
 // Add fields to the current view subform

← Older revision		Revision as of 17:33, 24 February 2011
Line 287:		Line 287:

	The view as map option is configured within the [[Settings.php]] file and not in the module specific settings.		The view as map option is configured within the [[Settings.php]] file and not in the module specific settings.
		+
		+	====User Field Configuration====
		+	As of v0.8 the user can add or remove fields to any of the views available on the data_view page. This is the sf_conf for the subform that is used to add/remove fields. The fields listed here are the fields that the admin wishes to make available to the user as options for adding to the view. Keeping the list short can help to make the user interface easier to understand.
		+	<br>
		+	Fields in this list MUST have field_id set up (correctly) in [[field_settings.php]]
		+	<pre>
		+	// Add fields to the current view subform
		+	$conf_mac_userconfigfields =
		+	array(
		+	'view_state' => 'max',
		+	'edit_state' => 'view',
		+	'sf_nav_type' => 'none',
		+	'sf_title' => 'userconfigfields',
		+	'sf_html_id' => 'mac_userconfigfields', // Must be unique
		+	'script' => 'php/data_view/subforms/sf_userconfigfields.php',
		+	'op_label' => 'space',
		+	'op_input' => 'go',
		+	'op_modtype' => FALSE,
		+	'fields' => // these are the fields available to the user - only fields with 'field_id' work
		+	array(
		+	$conf_field_itemkey,
		+	$conf_field_cxttype,
		+	$conf_field_smyinterp,
		+	$conf_field_dr,
		+	$conf_field_finish,
		+	$conf_field_short_desc,
		+	),
		+	);
		+	</pre>

	===XMI View===		===XMI View===

@@ Line 280: / Line 280: @@
 );
 </pre>
 ====Map====

@@ Line 265: / Line 265: @@
 ====Text====
+In our mod_cxt_settings.php example, the data view configuration for the text view looks like this:
 <pre>
 $conf_mac_text =

@@ Line 264: / Line 264: @@
 *'''fields'' - an array of fields to be displayed in the table
-====Chat====
+====Text====
-The view as chat option is dictated by the results array, and will automatically return any fields which satisfy the search query.  No additional configuration is required.
+The view as chat option is dictated by the results array, and will automatically return any fields which satisfy the search query.
 ====Map====

@@ Line 62: / Line 62: @@
 *[[sf_delete_record]] - Performs delete record function
 *[[sf_itemval]] - To be used for editing itemvals
 ===Spatial Data===

@@ Line 60: / Line 60: @@
 *[[sf_modtype_conflicts]] - To be used for editing modtypes
 *[[sf_dnarecord]] - Displays the 'dna' of a record to administrator, shows individual data fragments attached to record during the delete process
-*[[sf_deleterecord]] - Performs delete record function
+*[[sf_delete_record]] - Performs delete record function
 *[[sf_itemval]] - To be used for editing itemvals