The XML file is layed out using several sections. These sections relate to variables that are used within horde. Here is an example XML snippet and the resulting configuration file entries:

<?xml version="1.0"?>
<!-- $Horde: $ -->
 <configsection name="wicked">
  <configheader>Application Settings</configheader>

  <configstring name="notify_address" desc="The email address to which changes
   on pages should be mailed. Leave empty if you don't want notification
   messages to be sent." required="false" />
  <configenum name="diff_format" desc="The diff format that should be used when
   sending notifications.">unified
    <value desc="Unified context">unified</value>
    <value desc="Copied context">context</value>
    <value desc="Side by side">sidebyside</value>

<configuration> is the start of the config file.


<configsection name="wicked"> produces first level $conf['wicked'] variables.
Multiple configsection names produces multiple levels.

<configsection name="level1">
 <configsection name="level2">

produces $conf['level1']['level2'] variables.


<configheader> puts text to help organize the screen


<configstring ...> for selecting an item from a list


<configboolean ...>value</configboolean>

Enums (Select From a List)

<configenum ...>default_entry to provide a list of choices

within configenum section use:

  <value desc="List entry1">list1</value>
  <value desc="List entry2">list2</value>

Multi-Enums (Select Any Number From a List)

<configmultienum ...> for selecting multiple items from a list

Special Values

<configspecial application="horde" name="apps" /> - "values" list of active horde apps

See for a detailed explanation.


<configswitch ...> - mechanism for grouping sets of options
Use config entries from above to populate option choices.

<case ...> provides value for configswitch statement
Must reside within <configswitch> section