The calendar horizont, responsible for how far in the future unlimited repeating events get rendered,
would previously be moved to that date, even if it was far in the future like 2030.
Now all requests for more then 1000 days in the future get simply ignored."
The calendar horizont, responsible for how far in the future unlimited repeating events get rendered,
would previously be moved to that date, even if it was far in the future like 2030.
Now all requests for more then 1000 days in the future get simply ignored."
out-of-band data such as the HTTP user agent.
Use that to determine weither message fragmentation should be used or not.
Indicate that Funambol 6+ supports fragmentation (this solves cases where
big addressbooks cannot be syncrhonized because there are too many entries).
out-of-band data such as the HTTP user agent.
Use that to determine weither message fragmentation should be used or not.
Indicate that Funambol 6+ supports fragmentation (this solves cases where
big addressbooks cannot be syncrhonized because there are too many entries).
after selecting customfields with the columnselector, you can choose which customfields you want to display
in the customfields column with the columnselector. The header supports sorting and selecting.
Controling of the displayed customfields is done in uiinfolog, the action takes place in soinfolog
after selecting customfields with the columnselector, you can choose which customfields you want to display
in the customfields column with the columnselector. The header supports sorting and selecting.
Controling of the displayed customfields is done in uiinfolog, the action takes place in soinfolog
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')
pre_process_cf_header
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')
