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,
InfCloud 0.13.2.rc1
When a contact is synced in that has an FN field but no N field, the entry
in InfCloud becomes nameless. The contents of the FN seems to be ignored
completely.
Would it be possible (feasible, acceptable, allowed) to infer name fields
from FN?
-- Johan
I just realized that my infcloud Installation does no longer work.
In the javascript console, I can see:
Failed to load resource: the server responded with a status of 403 ()
for config.js
- checked the file permissions and it is 644 (folder infcloud is 755)
with correct owner.
As I did not change there anything recently, I wonder what might be the
Problem ?
any hints appreciated.
(infcloud version appears to be 0.13.1)
Hi,
I have a repeating entry that repeats every 30 days. It is some kind of todo
so when I took action I change the subject of the event by adding a
'checked' mark.
This leads to an event (ics) that has several VEVENTs. One is the 'main':
it describes the event and the RRULE. The others are modified occurrences
with RECURRENCE-IDs. See attachment 'previous.ics'.
Today I needed to move all upcoming events one day back. So I selected
'change all occurrences', 'repeat', and adjusted the date. The result can
be found in attachment 'current.ics'. However, no future events are shown
anymore.
One thing I noticed: in previous.ics all RECURRENCE-IDs reflect the
past dates and match DTSTART/DTEND.
RECURRENCE-ID;VALUE=DATE:20190102
RECURRENCE-ID;VALUE=DATE:20190201
RECURRENCE-ID;VALUE=DATE:20190303
RECURRENCE-ID;VALUE=DATE:20190402
RECURRENCE-ID;VALUE=DATE:20190502
RECURRENCE-ID;VALUE=DATE:20190601
RECURRENCE-ID;VALUE=DATE:20190701
But in the new event they became future dates and no longer match
DTSTART/DTEND:
RECURRENCE-ID;VALUE=DATE:20190730
RECURRENCE-ID;VALUE=DATE:20190829
RECURRENCE-ID;VALUE=DATE:20190928
RECURRENCE-ID;VALUE=DATE:20191027
RECURRENCE-ID;VALUE=DATE:20191126
RECURRENCE-ID;VALUE=DATE:20191226
RECURRENCE-ID;VALUE=DATE:20200125
Did I do anything wrong?
-- Johan
Hi,
For a long time I've been a happy user of DAViCal and clients. But I get
the feeling that over the years things are getting worse.
The problem? Appointments on my Android devices are not updated, or do not
propagate.
I am inclined to blame Android. Modern Android devices are so energy hungry
that they try to survive by putting draconian limits to honest Android apps.
In my setup, there is a DAViCal server that shares the data. On Android,
there's CalDAVsync that syncs DAViCal with the local calendar. The end
user tool is Business Calendar that operates on the local calendar. This is
a common type of setup used by most calendar apps and cloud calendars.
In earlier days these apps were all happily living (and running) in Android,
but nowadays they are put to sleep, stopped, thrown out, when the system
sees fit. As a result, appointments are no longer updated and propagated.
OTOH, Android is flexible so I assume there are settings to avoid this. So
my question is: what permissions or other settings do I need to give the
apps?
Thanks in advance,
Johan
Hi,
Suddenly I was missing some events. It took me some time to find out why.
When InfCloud starts up, it loads events between 3 months in the past and 3
months in the future (configurable, in my case it is 12 months both ways).
Now consider an event created April 1 2018 that repeats every 1st of the
month. Every month I change it (add a 'check' when it is past) so the
davical entry contains the actual VEVENT (with RRULE) and a huge list of
VEVENTs with RECURRENCE-IDs.
This event seems to be shown only if the starting date falls within the
months that are initially loaded.
When it is a simple repeating event (just an RRULE, no RECURRENCE-IDs) it
is shown correctly.
Any idea what is going on here?
-- Johan
If an event has a LAST-MODIFIED:
LAST-MODIFIED;VALUE=DATE-TIME:20190308T231001Z
this seems not to be recognized by InfCloud. As a result, when changing the
event via InfCloud, an additional LAST-MODIFIED is added:
LAST-MODIFIED:20190309T090207Z
...
LAST-MODIFIED;VALUE=DATE-TIME:20190308T231001Z
Other caldav systems, e.g. ownCloud, then reject this event as being
invalid.
I'm not quite sure who to blame...
-- Johan
Hello,
I have radicale running on my server and run caldavzap on my laptop to
interact with it. The setup works fine, however I have quite a few
lists and I would like to (down)load all lists but activate only one.
From my understanding i have to change line 616 of config js:
var
globalActiveTodoCollections=['https://IP/radicale/USER/5285f224-a8b3-63fe-8324-c9b053a67d79/'];
however, this doesnt work. I really tried everything I could think of,
for example the syntax for the globalCalendarSelecter (which works) and
anything similar. If I dont insert the full https address, the Browser
console gives me this error:
TypeError: globalSettings.activetodocollections.value[i].match(...) is
null
From what I understand the code tries to loop over the items in the
array and perform a regex on them to extract relevant data. But I can't
extract the required syntax from the code.
Google or similar doesnt yield any results. I hope you people can help
me, it would be greatly appreciated.
Regards,
Jacob
Estic de vacances fins el dia 24 de Septembre
Qualsevol dubte contacteu amb el Juanjo Perez juanjo.perez(a)bonarea.com
CONFIDENCIALITAT. Aquesta comunicació i els seus annexes contenen informació confidencial i/o secreta, sotmesa a secret professional i que té com a destinatari única i exclusivament a la persona a la que va dirigida. Si vostè no és el destinatari, l'informem que no està autoritzat a llegir-la, copiar-la o divulgar-la, de manera que li preguem que ho notifiqui immediatament a CORPORACIÓ ALIMENTARIA GUISSONA S.A. i desprès elimini aquest correu i qualsevol còpia del mateix. Queda, per tant,prohibida la lectura, divulgació o distribució d'aquest correu electrònic i dels seus annexes, a qualsevol persona que no sigui el seu destinatari, sense el consentiment escrit de CORPORACIÓ ALIMENTARIA GUISSONA S.A. PROTECCIÓ DE DADES. De conformitat amb el disposat en la normativa vigent en matèria de protecció de dades, li comuniquem que les dades de caràcter personal utilitzades en aquest enviament es troben incloses en fitxers la titularitat dels quals correspon a CORPORACIÓ ALIMENTARIA GUISSONA
S.A. Tanmateix, l'informem que les dades contingudes en aquest enviament seran incorporades en fitxers de CORPORACIÓ ALIMENTARIA GUISSONA S.A. amb l'única finalitat de mantenir i administrar la relació establerta, de manera que seran conservades mentre existeixi un interès mutu i no seran comunicades a tercers excepte obligació legal. Per exercir els drets d'accés, rectificació, cancel·lació, oposició, limitació del tractament i portabilitat de les dades, s'haurà de dirigir per escrit, acreditant la seva identitat, a CORPORACIÓ ALIMENTARIA GUISSONA S.A. C/ Traspalau, 8, 25210 Guissona (Lleida) o fer-ho a través de la direcció de correu electrònic lopd(a)bonarea.com. Si considera que les seves dades no estan sent tractades segons estableix la llei podrà presentar una reclamació davant l'autoritat de control (http://www.agpd.es). Per més informació pot consultar la nostra Política de Privacitat (http://www.bonarea-agrupa.com/ca/public/PrivacyPolicy).
--------------------------------------------------------------------------------------------------------------------
CONFIDENCIALIDAD. Esta comunicación y sus anexos contienen información confidencial y/o secreta, sometida a secreto profesional y que tiene como destinatario único y exclusivo la persona a la que va dirigida. Si usted no es el destinatario, le informamos que no está autorizado a leerla, copiarla o divulgarla, por lo que le rogamos que lo notifique inmediatamente a CORPORACIÓN ALIMENTARIA GUISSONA S.A. y tras ello elimine este correo y cualquier copia del mismo. Queda, por tanto, prohibida la lectura, divulgación o distribución de este correo electrónico y de sus anexos, a cualquier persona que no sea su destinatario, sin el consentimiento escrito de CORPORACIÓN ALIMENTARIA GUISSONA S.A. PROTECCIÓN DE DATOS. De conformidad con lo dispuesto en la normativa vigente en materia de protección de datos, le comunicamos que los datos de carácter personal utilizados en este envío se encuentran incluidos en ficheros cuya titularidad ostenta CORPORACIÓN ALIMENTARIA GUISSONA S.A. Asimismo, le inf
ormamos que los datos contenidos en este correo y los que lo sucedan, así como sus anexos o fax, serán incorporados a los ficheros de CORPORACIÓN ALIMENTARIA GUISSONA S.A. con la única finalidad de mantener y administrar la relación establecida, de forma que serán conservados mientras exista un interés mutuo para ello y no serán comunicados a terceros salvo obligación legal. Para ejercitar los derechos de acceso, rectificación, cancelación, oposición, limitación y portabilidad, deberá dirigirse por escrito, acreditando su identidad, a CORPORACIÓN ALIMENTARIA GUISSONA S.A. C/ Traspalau 8, 25210 Guissona (Lleida) o hacerlo a través de la dirección de correo electrónico lopd(a)bonarea.com. Si considera que sus datos no están siendo tratados según establece la ley podrá presentar una reclamación ante la autoridad de control (http://www.agpd.es). Para más información puede consultar nuestra Política de Privacidad (http://www.bonarea-agrupa.com/ca/public/PrivacyPolicy).
-----------------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY. This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication, along with any documents, files or attachments, may not be reproduced or distributed without the express written consent of CORPORACIÓN ALIMENTARIA DE GUISSONA, S.A. DATA PROTECTION. In compliance with the Personal Data Protection Law and GDPR we inform you that your personal information is included in a personal information filing system owned by CORPORACIÓN ALIMENTARIA DE GUISSONA, S.A
. We also inform you that your personal information included in this email, along with any documents, files or attachments, will be included in a personal information filing system owned by CORPORACIÓN ALIMENTARIA DE GUISSONA S.A. You may exercise your rights of access, rectification, cancellation, objection, portability and restriction of processing of your personal data, at any time, by sending a written notice, attaching a photocopy of a document evidencing your identity, to CORPORACIÓN ALIMENTARIA GUISSONA S.A. C/ Traspalau 8, 25210 Guissona (Lleida), or to lopd(a)bonarea.com. If you consider that we are not processing your personal data as required by law, you can exercise your right to lodge a complaint with a supervisory authority (http://www.agpd.es). For more information, you may visit our Privacy Policy (http://www.bonarea-agrupa.com/ca/public/PrivacyPolicy).
