What support can I expect for recurring tasks?

Manfred, Felix,

I have to come back to my issues with recurring tasks. I applied a few fixes in backend/kopano/mapiprovider.php that were part of my problems, but there is still one thing I can’t fix myself. Of course, I’m willing to share my current thoughts and code modifications, but I’m far from a professional programmer. You might cry when you see what I did to fix broken things :-)

I can clearly proof that a recurring to-do breaks after it’s updated on the mobile device. As a result, I get this in z-push-error.log:

01/12/2018 14:25:17 [29250] [WARN] [someuser] /usr/share/z-push-2.4.5/backend/kopano/mapi/class.taskrecurrence.php:104 Undefined offset: -2138701566 (8)
01/12/2018 14:25:17 [29250] [WARN] [someuser] /usr/share/z-push-2.4.5/backend/kopano/mapi/class.taskrecurrence.php:105 Invalid argument supplied for foreach() (2)

My Kopano license is paid.

What support for recurring tasks can I expect when I open a support call and spend my support time for having a bug fixed? Are recurring tasks supported anyway?

Yours,

Peter

Hi @itserv ,

@itserv said in What support can I expect for recurring tasks?:

What support for recurring tasks can I expect when I open a support call and spend my support time for having a bug fixed? Are recurring tasks supported anyway?

My statement in https://forum.kopano.io/post/10299 was more of a general nature, instead of a “what can be done in the name of the community”.

@itserv said in What support can I expect for recurring tasks?:

My Kopano license is paid.

I know. I looked up your subscription before answering your original question.

This of course does not mean that this can change if it becomes relevant in other customer projects, or once WebApp actually support recurring tasks. For the moment it’s just not economical to spend multiple days or research, implementation and testing on this.

Felix,

thank you for your reply, and I apologize to have forgotton I asked this question before. Your statement in the other thread is more than clear.

Yours,

Peter