Hi,
Using InfCloud 0.13.2.rc1 with Chrome, I can no longer add a photo. Everything looks normal, until I save the entry. No errors are given but the resultant entry has no photo.
When I modify (e.g. phone number) of an existing entry with a photo, the photo disappears. The existing photo on the server was a png.
FireFox seems to have no problems with this.
Errors as shown bij the Chromium debugger:
GET data:image/jpeg;base64,, net::ERR_INVALID_URL data_process.js:6357
Maybe related to config.js:
var globalContactPhotoType='jpeg';
???
-- Johan
Hi Johan,
please send me a private e-mail with the text file of the problematic vCard and steps to reproduce the problem.
Cheers,
JM
On 11 Dec 2015, at 12:11, Johan Vromans jvromans@squirrel.nl wrote:
Hi,
Using InfCloud 0.13.2.rc1 with Chrome, I can no longer add a photo. Everything looks normal, until I save the entry. No errors are given but the resultant entry has no photo.
When I modify (e.g. phone number) of an existing entry with a photo, the photo disappears. The existing photo on the server was a png.
FireFox seems to have no problems with this.
Errors as shown bij the Chromium debugger:
GET data:image/jpeg;base64,, net::ERR_INVALID_URL data_process.js:6357
Maybe related to config.js:
var globalContactPhotoType='jpeg';
???
-- Johan
On Fri, 11 Dec 2015 12:25:03 +0100 Ján Máté jan.mate@inf-it.com wrote:
please send me a private e-mail with the text file of the problematic vCard and steps to reproduce the problem.
Will do (later tonight).
Dear Jan,
I'd like to add my problem here because I can imagine that it is somehow connected to the issue here...
I am using carddavmate 0.13.1 to edit the entries in my davical server. Since a couple of weeks
Every time I edit an entry (not the contact photo but e.g. the address) the contact photo seems to be converted into PNG. The vcard file says: PHOTO;ENCODING=b;TYPE=png:data:image/png;base64, .....
Unfortunately some other clients I use with this server do not show the contact photo any more. Especially I use the carddav-sync app on my android cell phone.
You might be saying this is an incompatibility issue for the other clients and I am quite sure you are right. But maybe you have some other hint for me to solve this problem or at least convince carddavmate to leave the image format unchanged when saving the address entry.
By the way: I am using carddavmate for some years now ( and I love it ;-) ) and never had this problems before...
Thanx in advance!
Cheers,
Gerald
Am 11.12.2015 um 12:25 schrieb Ján Máté:
Hi Johan,
please send me a private e-mail with the text file of the problematic vCard and steps to reproduce the problem.
Cheers,
JM
On 11 Dec 2015, at 12:11, Johan Vromans jvromans@squirrel.nl wrote:
Hi,
Using InfCloud 0.13.2.rc1 with Chrome, I can no longer add a photo. Everything looks normal, until I save the entry. No errors are given but the resultant entry has no photo.
When I modify (e.g. phone number) of an existing entry with a photo, the photo disappears. The existing photo on the server was a png.
FireFox seems to have no problems with this.
Errors as shown bij the Chromium debugger:
GET data:image/jpeg;base64,, net::ERR_INVALID_URL data_process.js:6357
Maybe related to config.js:
var globalContactPhotoType='jpeg';
???
-- Johan
On Mon, 21 Dec 2015 07:35:02 +0100 Gerald Rausch rausch@web-rausch.de wrote:
Every time I edit an entry (not the contact photo but e.g. the address) the contact photo seems to be converted into PNG. The vcard file says: PHOTO;ENCODING=b;TYPE=png:data:image/png;base64, .....
Interesting...
Grepping my contacts[*] it seems that clients have gone wild.
PHOTO;ENCODING=b;TYPE=jpeg:iVBORw0KGg... all data in one line
PHOTO;ENCODING=b;TYPE=jpeg:/9j/4AAQSk... all data in one line
PHOTO;ENCODING=b;TYPE=png:iVBORw0KGgo... all data in one line
PHOTO;ENCODING=B;TYPE=png: iVBORw0KGgoAA... data broken in 76-byte lines
PHOTO;ENCODING=B;TYPE=JPEG;VALUE=BINARY:iVBORw0KGgoAA... all data in one line
PHOTO;ENCODING=b;TYPE=PNG;X-ABCROP-RECTANGLE=ABClipRect_1&0&28&246&246&z 5fNmNRbVNbd27D0BTkPsw==:iVBORw0KGgo...
Note that many TYPE=JPEG photos are really PNGs.
-- Johan
[*] http://www.gossamer-threads.com/lists/davical/general/2639#2639
Ok, I also checked once again:
This is part of the 'original' vcard dataset
PHOTO;TYPE=jpeg;ENCODING=b:iVBORw0KGgoAAAANSUhEUgAAAPYAAAESCAYAAAD[...]
When I edit this entry (leave the contact photo unchanged) this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
Gerald
Am 21.12.2015 um 08:11 schrieb Johan Vromans:
On Mon, 21 Dec 2015 07:35:02 +0100 Gerald Rausch rausch@web-rausch.de wrote:
Every time I edit an entry (not the contact photo but e.g. the address) the contact photo seems to be converted into PNG. The vcard file says: PHOTO;ENCODING=b;TYPE=png:data:image/png;base64, .....
Interesting...
Grepping my contacts[*] it seems that clients have gone wild.
PHOTO;ENCODING=b;TYPE=jpeg:iVBORw0KGg... all data in one line
PHOTO;ENCODING=b;TYPE=jpeg:/9j/4AAQSk... all data in one line
PHOTO;ENCODING=b;TYPE=png:iVBORw0KGgo... all data in one line
PHOTO;ENCODING=B;TYPE=png: iVBORw0KGgoAA... data broken in 76-byte lines
PHOTO;ENCODING=B;TYPE=JPEG;VALUE=BINARY:iVBORw0KGgoAA... all data in one line
PHOTO;ENCODING=b;TYPE=PNG;X-ABCROP-RECTANGLE=ABClipRect_1&0&28&246&246&z 5fNmNRbVNbd27D0BTkPsw==:iVBORw0KGgo...
Note that many TYPE=JPEG photos are really PNGs.
-- Johan
[*] http://www.gossamer-threads.com/lists/davical/general/2639#2639
Will check & fix asap (i'm currently extremely busy).
JM
On 22 Dec 2015, at 9:42 AM, Gerald Rausch rausch@web-rausch.de wrote:
Ok, I also checked once again:
This is part of the 'original' vcard dataset
PHOTO;TYPE=jpeg;ENCODING=b:iVBORw0KGgoAAAANSUhEUgAAAPYAAAESCAYAAAD[...]
When I edit this entry (leave the contact photo unchanged) this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
Gerald
Am 21.12.2015 um 08:11 schrieb Johan Vromans: On Mon, 21 Dec 2015 07:35:02 +0100 Gerald Rausch rausch@web-rausch.de wrote:
Every time I edit an entry (not the contact photo but e.g. the address) the contact photo seems to be converted into PNG. The vcard file says: PHOTO;ENCODING=b;TYPE=png:data:image/png;base64, .....
Interesting...
Grepping my contacts[*] it seems that clients have gone wild.
PHOTO;ENCODING=b;TYPE=jpeg:iVBORw0KGg... all data in one line
PHOTO;ENCODING=b;TYPE=jpeg:/9j/4AAQSk... all data in one line
PHOTO;ENCODING=b;TYPE=png:iVBORw0KGgo... all data in one line
PHOTO;ENCODING=B;TYPE=png: iVBORw0KGgoAA... data broken in 76-byte lines
PHOTO;ENCODING=B;TYPE=JPEG;VALUE=BINARY:iVBORw0KGgoAA... all data in one line
PHOTO;ENCODING=b;TYPE=PNG;X-ABCROP-RECTANGLE=ABClipRect_1&0&28&246&246&z 5fNmNRbVNbd27D0BTkPsw==:iVBORw0KGgo...
Note that many TYPE=JPEG photos are really PNGs.
-- Johan
[*] http://www.gossamer-threads.com/lists/davical/general/2639#2639
On Tue, 22 Dec 2015 10:27:08 +0100 Ján Máté jan.mate@inf-it.com wrote:
Will check & fix asap (i'm currently extremely busy).
Any progress on this one?
-- Johan
Sorry no :-(
Sometime in next week I will go abroad for ~2 weeks (Corfu). Then (when I return) I will have time to work on InfCloud ...
Cheers,
JM
On 27 Feb 2016, at 15:27, Johan Vromans jvromans@squirrel.nl wrote:
On Tue, 22 Dec 2015 10:27:08 +0100 Ján Máté jan.mate@inf-it.com wrote:
Will check & fix asap (i'm currently extremely busy).
Any progress on this one?
-- Johan
On Tue, 22 Dec 2015 09:42:16 +0100 Gerald Rausch rausch@web-rausch.de wrote:
This is part of the 'original' vcard dataset
PHOTO;TYPE=jpeg;ENCODING=b:iVBORw0KGgoAAAANSUhEUgAAAPYAAAESCAYAAAD[...]
So it says it's a JPEG, but it is really a PNG.
When I edit this entry (leave the contact photo unchanged)
What client? If CardDAVMate, what browser?
this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
The photo contents looks unmodified, but now it is (correctly!) registered as a PNG.
But I assume the photo does not get lost, as it is in my case?
-- Johan
Am 22.12.2015 um 10:34 schrieb Johan Vromans:
this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
The photo contents looks unmodified, but now it is (correctly!) registered as a PNG.
Note that this is PHOTO property is only valid when used in vCard 4.0. In vCard 3.0 the entry should look like
PHOTO;ENCODING=b;TYPE=png:iVBORw0KGgoAAAANSU[...]
or
PHOTO;ENCODING=b;TYPE=png;VALUE=URI:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
Though, the latter may not be well supported by vCard 3.0 clients.
In vCard 3.0 the default value type is "binary" whereas in vCard 4.0 the only allowed value type is "uri".
cheers
Marten
Am 22.12.2015 um 22:29 schrieb Marten Gajda:
[...]
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU
[...]
The photo contents looks unmodified, but now it is (correctly!) registered as a PNG.
[...]
I don't think the content is unmodified. Although the first few characters seem to be identical, they begin to differ later...
Ok then, I did some further testing:
1. prepared two pictures, 1 jpeg 1 png 2. added one address entry with the jpeg contact photo 3. added one address entry with png contact photo client was CardDAVMate 0.13.1 browser was Firefox 43.0
Result:
for the jpeg dataset:
BEGIN:VCARD VERSION:3.0 UID:x10h9kx8-upx3-td85-lvr3-4560vcvafvv2 N:Aa;Jpeg;;; FN:Aa Jpeg REV:20151223T075141Z PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA [many more lines to follow here]
for the png dataset:
BEGIN:VCARD VERSION:3.0 UID:2q2cq44l-qw5t-caqn-s62a-ke657xr0jo9a N:Aa;Png;;; FN:Aa Png REV:20151223T075639Z PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA [may more lines to follow here...]
Both vcf files have almost the same size.
So CardDAVMate seems to convert the jpeg picture into png. So far so good. Unfortunately, some other clients do not show up the pictures in the address book after syncing. E.g. android smart phone with carddavsync and thunderbird with SOGo Connector. Both clients worked fine until some weeks (months?) ago. In CardDAVMate both pictures show up just fine!
Any ideas?
Cheers,
Gerald
Am 22.12.2015 um 10:34 schrieb Johan Vromans:
On Tue, 22 Dec 2015 09:42:16 +0100 Gerald Rausch rausch@web-rausch.de wrote:
This is part of the 'original' vcard dataset
PHOTO;TYPE=jpeg;ENCODING=b:iVBORw0KGgoAAAANSUhEUgAAAPYAAAESCAYAAAD[...]
So it says it's a JPEG, but it is really a PNG.
When I edit this entry (leave the contact photo unchanged)
What client? If CardDAVMate, what browser?
this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
The photo contents looks unmodified, but now it is (correctly!) registered as a PNG.
But I assume the photo does not get lost, as it is in my case?
-- Johan
Hi Gerald,
see: https://www.inf-it.com/mlmmj/davclients/2015-09/0000064.html https://www.inf-it.com/mlmmj/davclients/2015-09/0000064.html
JM
On 23 Dec 2015, at 09:49, Gerald Rausch rausch@web-rausch.de wrote:
Ok then, I did some further testing:
- prepared two pictures, 1 jpeg 1 png
- added one address entry with the jpeg contact photo
- added one address entry with png contact photo
client was CardDAVMate 0.13.1 browser was Firefox 43.0
Result:
for the jpeg dataset:
BEGIN:VCARD VERSION:3.0 UID:x10h9kx8-upx3-td85-lvr3-4560vcvafvv2 N:Aa;Jpeg;;; FN:Aa Jpeg REV:20151223T075141Z PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA [many more lines to follow here]
for the png dataset:
BEGIN:VCARD VERSION:3.0 UID:2q2cq44l-qw5t-caqn-s62a-ke657xr0jo9a N:Aa;Png;;; FN:Aa Png REV:20151223T075639Z PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA [may more lines to follow here...]
Both vcf files have almost the same size.
So CardDAVMate seems to convert the jpeg picture into png. So far so good. Unfortunately, some other clients do not show up the pictures in the address book after syncing. E.g. android smart phone with carddavsync and thunderbird with SOGo Connector. Both clients worked fine until some weeks (months?) ago. In CardDAVMate both pictures show up just fine!
Any ideas?
Cheers,
Gerald
Am 22.12.2015 um 10:34 schrieb Johan Vromans:
On Tue, 22 Dec 2015 09:42:16 +0100 Gerald Rausch rausch@web-rausch.de wrote:
This is part of the 'original' vcard dataset
PHOTO;TYPE=jpeg;ENCODING=b:iVBORw0KGgoAAAANSUhEUgAAAPYAAAESCAYAAAD[...]
So it says it's a JPEG, but it is really a PNG.
When I edit this entry (leave the contact photo unchanged)
What client? If CardDAVMate, what browser?
this is what happens to the photo:
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBORw0KGgoAAAANSU[...]
The photo contents looks unmodified, but now it is (correctly!) registered as a PNG.
But I assume the photo does not get lost, as it is in my case?
-- Johan
On Wed, 23 Dec 2015 10:15:57 +0100 Ján Máté jan.mate@inf-it.com wrote:
see: https://www.inf-it.com/mlmmj/davclients/2015-09/0000064.html https://www.inf-it.com/mlmmj/davclients/2015-09/0000064.html
This fix is already included in 0.13.2.rc1 (and modified to use globalContactPhotoType instead of the fixed string 'png').
-- Johan
-
Gerald Rausch -
Johan Vromans -
Ján Máté -
Marten Gajda