In your application/templates/default directory, create a new template file named 'config.tpl'. This will be included by config.php and used to draw the page. This template should include a POST method form. The following template tags may be used:
Note the fieldname, newsettings[contact_application]. This array name must be used for the form values. Next, note the value setting for this form element, {value_contact_application}. This indicates that we want the current value of the config setting, 'contact_application', to be set and displayed on the form. Lastly, look at the template element, {lang_Contact_application}. Here, the value from the lang db table will be inserted if available.
</para>
<para>
Let's take a look at part of the preferences/default/config.tpl:
At each invocation of config.php, a call to the common class function hook_single() is made. It attempts to include a file, hook_config.inc.php as a set of code for config.php to use. In the case of the preferences example above, using hook_country_set, here is the corresponding function in preferences/inc/hook_config.inc.php:
Note again the template value we used earlier, {hook_country_set}. This causes config.php to look for a function named country_set(). Since we included the file with this function via the hook_single() call, this function is executed. It's return is a string, and the function prints nothing itself.
</para>
</sect2>
<sect2>
<title>
hook_config_validate.inc.php (optional)
</title>
<para>
Once the admin clicks the submit button to post the form, we can optionally validate their input using one or many different functions. This is done by first making another call to hook_single() in the API common class. This time, the name config_validate is used, so common tries to include 'application/inc/hook_config_validate.inc.php'.
</para>
<para>
If this file exists, it sets a var to tell config.php it was found. Following then are functions named after each config we want to validate. The following example is for addressbook:
Here we created a function to check the entered value for the config item, ldap_contact_context. We want to make sure the admin did not set this value to one which would conflict with another config item, used for accounts or groups in eGroupWare.
config.php calls this function, sending it the POSTed value. config.php continues, adding all other config items from the POSTed values.
</para>
<para>
The variable $GLOBALS['config_error'] is parsed through lang(), then appended to the local variable, $error. If this has any value after the POSTed variables are checked, the form then has its {error} tag filled with this result. The form is displayed again, with the error. If $error has no value, config.php redirects to admin/index.php.
</para>
<para>
However, there is one more function that may be included in hook_config_validate.inc.php:
</para>
<programlisting>
<![ CDATA [ /* Check all settings to validate input. Name must be 'final_validation' */
]]><![ CDATA [ function final_validation($value='')
]]><![ CDATA [ $GLOBALS['config_error'] = 'Contact context must be set';
]]><![ CDATA [ }
]]><![ CDATA [ else
]]><![ CDATA [ {
]]><![ CDATA [ $GLOBALS['config_error'] = '';
]]><![ CDATA [ }
]]><![ CDATA [ }
]]> </programlisting>
<para>
config.php checks for the existence of the function 'final_validation()'. This function can be used to check all form values at once. It gets sent the entire $newsettings array POSTed from the form. As with the other functions in this file, final_validation() should set $GLOBALS['config_error'] if there is a problem.
