Tickets :: Comment on [#7407] Photos: storing in LDAP and broken contact sync

* Your Email Address
* Spam protection	Enter the letters below: . ..__ __. __.. . \| \|[ __(__ (__ \| \| \|/\\|[_./.__).__)\|/\\|
Comment	>> 2) base64 is terminated by a blank line, so eliminate it before > >> matching the following vCalender attributes. Otherwise the name of > >> one following PHOTO will start with a \r\n, so it will be > >> discarded afterward > > > > This change is not necessary. The attribute is parsed fine with the > extra blank line already. > > > >> 4) In toHash and tovCard, the encoding of a photo is tested against > >> and set to 'b'. Is that a valid encoding name at all? Changed > >> it to 'base64' and it worked again. In turba/lib/Driver.php > > > > It's actually the only valid value. BASE64 is not valid and breaking > RFCs. We are reading it now anyway. > > > >> 5) Finally, how am I supposed to delete a photo from a contact or save > > > > Not at all, yet. > > > >> it to a local file (e.g. for doing some cropping stuff in an external > >> tool)? There are no delete and save buttons as for a common file. > > > > Right mouse click. > > > >> PS: any thoughts on adding crop support? Photos taken by mobiles have > >> a stupid format for contact photos. Otherwise, I could live with as > >> save as local file button. > > > > That would be nice indeed, and would have to be added to > Horde_Form_Type_image. Please file a separate enhancement request for > that.
Attachment
Watch this ticket