[turba] additional contact fields and activesync
Simon Brereton
simon.brereton at dada.net
Thu Apr 28 17:24:50 UTC 2011
> -----Original Message-----
> From: Ulli [mailto:ulli_um at arcor.de]
> Sent: Thursday, April 28, 2011 12:44 PM
> Why do we not go with the following proposal of Simon Brereton
>
> email1 = Home
> email2 = Work
> email3 = Spare
>
> With this configuration the clients which supports preferred emails
> will identify the home address as preferred and work as additional.
> The other devices just show the two email entry.
>
> Regarding the additional cell phone number. I have found the
> following two entry in the attributes.php file of turba/config.
>
> $attributes['homePhone'] = array(
> 'label' => _("Home Phone"),
> 'type' => 'phone',
> 'required' => false
> );
> $attributes['workPhone'] = array(
> 'label' => _("Work Phone"),
> 'type' => 'phone',
> 'required' => false
> );
>
> what is the "carPhone*" entry about? is this the additional field
> which will be supported by the activesync protocol?
>
>
> Is there a version available which I could use for a first try if the
> fix works?
Mainly because my idea was pants - and Andrea's idea was better (and conforms to what passes for a standard in this this field - i.e. it will have the least amount of negative impact - and ultimately since there is no real standard, any implementation will have some negative impact somewhere.
Carphone - as discussed in the other thread - is a legacy implementation. It would be far more useful to keep it, but add additional cell-phone entries. Which thankfully, it looks like Michael has agreed to implement support thereof.
Simon
More information about the turba
mailing list