Select options can be provided using one of three different methods:
1. key=value pairs, one per line, as for a selectbox
2. @filename.php - The file must be in the egw root, and define an array named $options, that has key => value pairs
3. Define the options normally used for the AJAX Select widget (get_rows, get_title, id_field) and it will pull values from the database, as normal.
Other options (icon, filter, template, link) can be used regardless of the method used to get the values.
# support for size options in url-phone customfield
# support for size options in url-email customfield
# allowing additional parameters to be passed to the link created from the url-email
function to display the customfields in a nextmatch table-header with the functionality of sorting and selecting
by customfields. Of cource you need to adapt the source of your get_rows or search functionality to do the
actual sorting and selecting. We try to do some additional documentation in codecorner
You can pass the allowed/wanted fields to the header by passing an array of the wanted fields to the widget
through the options parameter (see the eTemplate editor for fields/cells). This array is passed on through
$cell['size']. By now the array passed through is only working, if it is the only entry in the optionsparameter.
The allowed fields array assumes an numerical indexed array of (an) array(s) with ['name'] tag(s) set.
The name provided assumes a preceding #. (e.g.: $allowed_fields[x]['name']='#MyCustomField')
identify which customfield is displayed (onmouseover), a click on the icon of the customfield opens the description of that field as
alertbox. Also added the possibility to set an textfield/textarea to readonly with the option readonly=readonly, so users may not be able to change
values of e.g.: external keys
- also lookup the custom fields from the app mentioned in the template, if there no cfs for the current app, eg. sitemgr contactform
- forward the needed attribute to the cf
- alignment (no spacing, padding) if there are no labels"
Admin can now define multiple addressbooks each with an own edit / view template and an own icon.
Atm. all Addressbooks are stored in one backend, but this will change soon^tm
