Fixed documentation typo for column names

The field name for additional information is additional_info rather than additional_information.
mantisbt · Feb 28, 2012 · ab0f381 · ab0f381 · atrol · Feb 28, 2012
1 parent 7caa180
commit ab0f381
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/config_defaults_inc.php b/config_defaults_inc.php
@@ -829,7 +829,7 @@
 	 * reproducibility, status, resolution, category_id, date_submitted, last_updated,
 	 * os, os_build, platform, version, fixed_in_version, target_version, view_state,
 	 * summary, sponsorship_total, due_date, description, steps_to_reproduce,
-	 * additional_information, attachment_count, bugnotes_count, selection, edit,
+	 * additional_info, attachment_count, bugnotes_count, selection, edit,
 	 * overdue
 	 *
 	 * @global array $g_view_issues_page_columns

diff --git a/docbook/adminguide/en/configuration.sgml b/docbook/adminguide/en/configuration.sgml
@@ -745,7 +745,7 @@
                 <term>$g_view_issues_page_columns</term>
                 <listitem>
                     <para>This configuration option is used to select the columns to be included in the View Issues page and in which order.  If one of the column is not accessible to the logged in user, or corresponds to a disabled feature, then it will be automatically removed from the list at runtime.  Hence, the same column list may show a different set of columns based on the logged in user, the currently selected project and enabled features (e.g. sponsorship_total is only shown if the sponsorship feature is enabled).</para>
-                    <para>The supported columns are: selection, edit, id, project_id, reporter_id, handler_id, priority, reproducibility, projection, eta, resolution, fixed_in_version, view_state, os, os_build, build (for product build), platform, version, date_submitted, attachment_count, category, sponsorship_total, severity, status, last_updated, summary, bugnotes_count, description, steps_to_reproduce, additional_information.  As for custom fields they can be referenced by adding a 'custom_' to their name (e.g. xyz would be custom_xyz).</para>
+                    <para>The supported columns are: selection, edit, id, project_id, reporter_id, handler_id, priority, reproducibility, projection, eta, resolution, fixed_in_version, view_state, os, os_build, build (for product build), platform, version, date_submitted, attachment_count, category, sponsorship_total, severity, status, last_updated, summary, bugnotes_count, description, steps_to_reproduce, additional_info.  As for custom fields they can be referenced by adding a 'custom_' to their name (e.g. xyz would be custom_xyz).</para>
                     <para>By default the following columns are selected: selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment_count, category_id, severity, status, last_updated, summary.</para>
                 </listitem>
             </varlistentry>