Ticket #133 (closed Bug: fixed)

Opened 7 years ago

Last modified 6 years ago

Using CALDAV calendars on Windows failed

Reported by: timm_r Owned by: Cyrus Daboo
Priority: major Milestone: Next
Component: Application Version: v4.0.6
Severity: Serious Keywords:
Cc: andrew@… Operating System: Windows
OS Version: XP SP2

Description

I created a caldav account pointing to a CALDAV server running rscds. When I login into the caldav server, Mulberry does not display the users/collections/calendar hierachies. I can create a sub-calendar (e.g. /timm/job, if timm is my username). I am also able to create events in this calendar, but after shutting down mulberry and starting again, Mulberry fails again to display the calendar hierachy and the events. The calendar/events are stored on the server, and send to Mulberry after request (PROPFIND), but Mulberry does not display them.

This only happens on Windows, Mulberry 4.06. Using Mulberry 4.07b1 on Mac OS X works without problems with the same account and server configuration.

I also had crashes after pressing the OK-button in the preferences, when I've changed anything in the CALDAV account settings (but they are stored nevertheless).

Change History

comment:1 Changed 7 years ago by karora

  • Cc andrew@… added

Hi,

This could well be a bug in RSCDS, of course, and I'd appreciate if you could help me ascertain that so I can fix it :-)

At present Mulberry 4.0.6 on Linux works fine for me with RSCDS, but I don't have access to a Windows box to see what might be going wrong. I will try and install Mulberry in Wine and see if I can find out what might be happening, at least from a protocol point of view.

Regards, Andrew McMillan?.

comment:2 Changed 6 years ago by Cyrus Daboo

  • Status changed from new to closed
  • Resolution set to worksforme

Any follow up on this? As far as I know CalDAV works the same on Windows as on other platforms. Its worth double-checking that the preferences are set exactly the same. Also getting a protocol log from the server woul dbe useful too.

Re-open if still a problem.

comment:3 Changed 6 years ago by Cyrus Daboo

  • Milestone unassigned deleted

comment:4 Changed 6 years ago by Cyrus Daboo

  • Status changed from closed to reopened
  • Resolution worksforme deleted

Re-opening as this is a bug.

comment:5 Changed 6 years ago by Cyrus Daboo

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Milestone set to Next

Problem with XML namespace parsing now fixed.

Note: See TracTickets for help on using tickets.