Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

New network calendar event, very slow to update on calendar view

  • 1 reply
  • 0 have this problem
  • 4 views
  • Last reply by EmmanuelT

more options

Hi,

I am using a network calendar (Thunderbird build-in, no add-ons) with "Offline support" installed on premises (NextCloud). The calendar works perfectly, updating network calendar as needed.

When I create a new event and press [Save and Close] button, the dialog box closes, but the event takes about 25-35 seconds to appear on the calendar.

When I delete the event it takes about 12-15 seconds to disappear from the view.

If the calendar is local (on the computer) the event appears immediately on the calendar view.

I presume that this has to do with the network update procedure. Is there a way (or an option) that would show the event immediately on the view and make the update on the background later on ?

My Thunderbird version is 115.1.0 (64-bit) installed on Microsoft Windows 11.

Thank you

Hi, I am using a network calendar (Thunderbird build-in, no add-ons) with "Offline support" installed on premises (NextCloud). The calendar works perfectly, updating network calendar as needed. When I create a new event and press [Save and Close] button, the dialog box closes, but the event takes about 25-35 seconds to appear on the calendar. When I delete the event it takes about 12-15 seconds to disappear from the view. If the calendar is local (on the computer) the event appears immediately on the calendar view. I presume that this has to do with the network update procedure. Is there a way (or an option) that would show the event immediately on the view and make the update on the background later on ? My Thunderbird version is 115.1.0 (64-bit) installed on Microsoft Windows 11. Thank you

Modified by EmmanuelT

All Replies (1)

more options

Solved it myself !

This is a NextCloud's specific version bug.

To solve it, you have to delete all records concerning your nextcloud login name directly on the mysql (mariadb) database, using the sql command:

delete from oc_authtoken where login_name = '<username>';

Check this link for more information on the issue: Several issues after upgrading to Nextcloud 21