Kontakt Calender saves changes to event locally. Change is not uploaded to IMAP. #61

Open
opened 4 months ago by martinhodges · 2 comments

Basic information

  • TDE version: R14.0.10
  • Distribution: Devuan Beowulf
  • Hardware: amd64

Description

This is a bug when the groupware functionality is used with a disconnected IMAP account.
Calender event may be edited and saved on one machine but the change is not reflected on another machine using the same dIMAP account. This defeates the whole purpose of this functionality for me.
...

Steps to reproduce

  1. Set up an IMAP account to use disconnected iMAP on several machines with groupware enabled.
  2. Create a calender event on one machine.
    2a. Upload the event to IMAP on the first machine. Refreshing the calender will not suffice. You must change to the email view and use F5 or Ctl-L.
    2b.Update the calender in the other machine. Again, refresh in the calender does not do anything for this. One must to the e-mail window and F5 or Ctl-L.
  3. Check that the event has propagated to the other machine.
  4. Modify the event on one machine.
  5. Observe that the modification has not been synchronised in the other machine.

I have observed two bugs that affect this issue.

  1. The kolab.xml in the Calender mail folder is not modified. Ovbviously nothing will happen on the other machine. Local changes in the calender will be lost when Kontakt is closed. Kontakt complains about the IMAP index on startup. This is not so easy to reproduce.

  2. The kolab.xml IS changed but the timestamp in the Calender folder is not. The XML content reflects the time stamp of the change and the new values but the 'mail' does not appear changed so the change is not uploaded to the IMAP account. These changes survive Kontact restarts.

Screenshots

<!-- This is a comment. Please fill in the required fields below. The comments provide instructions on how to do so. Note: You do not need to remove comments. --> ## Basic information - TDE version: R14.0.10<!-- such as R14.0.10 - see tde-config -v --> - Distribution: Devuan Beowulf<!-- such as Debian Buster - see lsb_release -sd --> - Hardware: amd64<!-- amd64 / i386 / armhf / ... --> <!-- Use SL/* labels to set the severity level. Please do not set a milestone. --> ## Description This is a bug when the groupware functionality is used with a disconnected IMAP account. Calender event may be edited and saved on one machine but the change is not reflected on another machine using the same dIMAP account. This defeates the whole purpose of this functionality for me. ... ## Steps to reproduce 1. Set up an IMAP account to use disconnected iMAP on several machines with groupware enabled. 2. Create a calender event on one machine. 2a. Upload the event to IMAP on the first machine. Refreshing the calender will not suffice. You must change to the email view and use F5 or Ctl-L. 2b.Update the calender in the other machine. Again, refresh in the calender does not do anything for this. One must to the e-mail window and F5 or Ctl-L. 3. Check that the event has propagated to the other machine. 4. Modify the event on one machine. 5. Observe that the modification has not been synchronised in the other machine. I have observed two bugs that affect this issue. 1) The kolab.xml in the Calender mail folder is not modified. Ovbviously nothing will happen on the other machine. Local changes in the calender will be lost when Kontakt is closed. Kontakt complains about the IMAP index on startup. This is not so easy to reproduce. 2) The kolab.xml IS changed but the timestamp in the Calender folder is not. The XML content reflects the time stamp of the change and the new values but the 'mail' does not appear changed so the change is not uploaded to the IMAP account. These changes survive Kontact restarts. ## Screenshots <!-- If it seems useful, please provide provide one or more screenshots. -->
Poster

Similar problem with editing exsisting contacts.

Similar problem with editing exsisting contacts.
martinhodges closed this issue 1 month ago
Owner

Hi @martinhodges, I guess you meant to add a comment and not close the issue, right?

Hi @martinhodges, I guess you meant to add a comment and not close the issue, right?
SlavekB reopened this issue 1 month ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.