1 Feb
2020
1 Feb
'20
8:57 a.m.
Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.
As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?
Kind regards,
--
Ismael
1 Feb
1 Feb
5:14 p.m.
Hi Ismael,
this bug is already fixed in the latest relase candidates. Here is the fix:
https://www.inf-it.com/fixes/photo_attr_fix.diff
<https://www.inf-it.com/fixes/photo_attr_fix.diff>
Cheers,
JM
On 1 Feb 2020, at 09:57, Ismael Bouya
<ismael(a)bouya.org> wrote:
Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.
As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?
Kind regards,
--
Ismael
5:18 p.m.
Hi Ján,
Thanks a lot for this patch!
Are non-released code available somewhere? I didn’t see any repository
or so on the website.
Kind regards,
(Sat, Feb 01, 2020 at 06:14:31PM +0100) Ján Máté :
Hi Ismael,
this bug is already fixed in the latest relase candidates. Here is the fix:
https://www.inf-it.com/fixes/photo_attr_fix.diff
<https://www.inf-it.com/fixes/photo_attr_fix.diff>
Cheers,
JM
On 1 Feb 2020, at 09:57, Ismael Bouya
<ismael(a)bouya.org> wrote:
Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.
As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?
Kind regards,
--
Ismael
Hi Ismael,
this bug is already fixed in the latest relase candidates. Here is the
fix:
[1]https://www.inf-it.com/fixes/photo_attr_fix.diff
Cheers,
JM
On 1 Feb 2020, at 09:57, Ismael Bouya <[2]ismael(a)bouya.org> wrote:
Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.
As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?
Kind regards,
--
Ismael
References
Visible links
1. https://www.inf-it.com/fixes/photo_attr_fix.diff
2. mailto:ismael@bouya.org
--
Ismael
5:31 p.m.
Hi Ismael,
see: https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html
<https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html>
JM
On 1 Feb 2020, at 18:18, Ismael Bouya
<ismael(a)bouya.org> wrote:
Hi Ján,
Thanks a lot for this patch!
Are non-released code available somewhere? I didn’t see any repository
or so on the website.
Kind regards,
(Sat, Feb 01, 2020 at 06:14:31PM +0100) Ján Máté :
Hi Ismael,
this bug is already fixed in the latest relase candidates. Here is the fix:
https://www.inf-it.com/fixes/photo_attr_fix.diff
<https://www.inf-it.com/fixes/photo_attr_fix.diff>
Cheers,
JM
On 1 Feb 2020, at 09:57, Ismael Bouya
<ismael(a)bouya.org> wrote:
Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.
As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?
Kind regards,
--
Ismael
Hi Ismael,
this bug is already fixed in the latest relase candidates. Here is the
fix:
[1]https://www.inf-it.com/fixes/photo_attr_fix.diff
Cheers,
JM
On 1 Feb 2020, at 09:57, Ismael Bouya <[2]ismael(a)bouya.org> wrote:
Hello all,
I’m using carddavmate and caldavzap for a long time, and I recently
uncovered an issue:
When I modify my contacts from infcloud, some of my pictures, the ones
that get stored in png, have a field that looks like:
-----
PHOTO;ENCODING=b;TYPE=png:data:image/png;base64,iVBO(...)
-----
when exported. It seems like this kind of formatting is not supported,
so I guess it’s not a standard one: when synchronizing with other
clients, like the stock android app or khard, they crash or are unable
to display the picture.
As soon as I remove the "data:image/png;base64," part of the field, it
starts working again. Is it an issue with infcloud? Note that it used to
work for a long time without any issue, and quite recently I
simultaneously upgraded and migrated from caldavzap+carddavmate to
infcloud. I’m not absolutely sure what changed, but maybe it will ring a
bell to some of you?
Kind regards,
--
Ismael
References
Visible links
1. https://www.inf-it.com/fixes/photo_attr_fix.diff
2. mailto:ismael@bouya.org
--
Ismael
5:35 p.m.
Thanks Ján!
Kind regards,
(Sat, Feb 01, 2020 at 06:31:34PM +0100) Ján Máté :
Hi Ismael,
see: https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html
<https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html>
--
Ismael
5:51 p.m.
Hi again Ján,
I confirm that the patch worked, thanks
Do you know if there is a way to mass-edit-an-save all contacts that I
have? (I have hundreds of them, it’s a bit difficult to edit them all
one by one)
I’m at ease with the web dev console and javascript, I just need a bit
of guidance with where the data are in InfCloud.
(Sat, Feb 01, 2020 at 06:35:08PM +0100) Ismael Bouya :
Thanks Ján!
Kind regards,
(Sat, Feb 01, 2020 at 06:31:34PM +0100) Ján Máté :
--
Ismael
Hi Ismael,
see: https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html
<https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html>
--
Ismael
5:56 p.m.
Hi Ismael,
sorry but there is no mass-edit action (there is no such thing in the CardDAV
specification). I recommend you to edit the data on the server (e.g. by a combination of
SQL UPDATE with a regex).
JM
On 1 Feb 2020, at 18:51, Ismael Bouya
<ismael(a)bouya.org> wrote:
Hi again Ján,
I confirm that the patch worked, thanks
Do you know if there is a way to mass-edit-an-save all contacts that I
have? (I have hundreds of them, it’s a bit difficult to edit them all
one by one)
I’m at ease with the web dev console and javascript, I just need a bit
of guidance with where the data are in InfCloud.
(Sat, Feb 01, 2020 at 06:35:08PM +0100) Ismael Bouya :
Thanks Ján!
Kind regards,
(Sat, Feb 01, 2020 at 06:31:34PM +0100) Ján Máté :
--
Ismael Hi Ismael,
see: https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html
<https://www.inf-it.com/mlmmj/davclients/2015-11/0000004.html>
--
Ismael
8:45 p.m.
Hi Ján,
I was afraid there were no such thing, but modifing the data on the
server didn’t exactly achieve what I want.
Here is what I got in the end, to run in the web console, in case it
would be useful to anyone:
----
for (contact of window.globalAddressbookList.contacts) {
if (contact.uid && contact.accountUID && contact.etag) {
window.globalAddressbookList.loadContactByUID(contact.uid);
window.dataToVcard(contact.accountUID, contact.uid,
globalRefAddContact.attr('data-filter-url'), contact.etag);
}
}
----
Thanks a lot for your help!
--
Ismael
1226
days inactive
1226
days old
7 comments
2 participants
participants (2)
-
Ismael Bouya -
Ján Máté