Problem connecting to a calendar in SM 2.53

[hardys]

I am not able, to connect to a calendar with Lightning 5.8 in SM 2.53.
In the error console I see this entry:

Code: Select all

Zeitstempel: 13.07.2019, 10:25:12
Fehler: [calCachedCalendar] replay action failed: null, uri=https://mail.xxx.de/calendars/xxx/Calendar/Stiftung, result=2147500037, operation=[xpconnect wrapped calIOperation]
Quelldatei: file:///C:/Users/xxx/AppData/Roaming/Mozilla/SeaMonkey/Profiles/xxx.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCachedCalendar.js
Zeile: 331

It also doesn't work when I disable offline support.
In SM 2.49.5 it works as expected with the same credentials and settings.

[therube]

Are you using the calendar (lightning) version from here, https://www.wg9s.com/comm-253/ ?

[hardys]

I have used this version from wg9s as well as the german version provided by frg. Both don't work

[therube]

(Oh, just babbling now... language packs ? maybe need to remove language pack first, install Calendar, then reinstall language pack?)

[frg]

I was able to reproduce it. Authorization prompt is missing. Might be a problem in Lightning or SeaMonkey. Will see that I fix is as fast as possible. Which means not before Saturday if it is an easy fixer

[hardys]

FYI: I have tried with SM 2.57 and my current profile. The calendars do not show at all, but when you choose "export calender" a window with all available calendars pops up and you can choose one for export and the export works, so in 2.57 the credentials are provided.

Edit: this is with Lightning 6.2.8.1 from wg9s

[frg]

This was broken by a mozilla anti-phishing fix.

Setting network.auth.non-web-content-triggered-resources-http-auth-allow to true fixes it for 2.53 and up. Works only by accident in 2.57 because mail is broken there right now.

It is either caldav or this fix:
https://bugzilla.mozilla.org/show_bug.cgi?id=1409449

FRG

[hardys]

Thank you frg for the fix.
Works as expected now

[frg]

> Thank you frg for the fix

Well I basically broke it too because I backported the orginal sec fix to 2.53

But finding a fix gave me the opportunity to learn about a feature I never used before so not in vain. And there will soon be 200 new backported patches in 2.53 because of it.

FRG