escoand/fullcalendar-plugins

fullcalendar-plugins's Issues

Date Format Compatibility Issue with Radicale CalDAV Server

Description

I am encountering a date format compatibility issue when using the FullCalendar plugin with the Radicale CalDAV server. The plugin sends dates in the "YYYYMMDDTHHMMSS" format, which Radicale does not seem to accept, leading to a "400 Bad Request" error.

Environment

• FullCalendar Version: v6.1.10
• FullCalendar CalDAV Plugin Version: [the latest version from CDN]
• Radicale Version: v2.1.12
• Browser and Version: Edge v119.0.2151.72
• Server: ubuntu (Cloud)
• Reverse Proxy: NGINX

Steps to Reproduce

1. Configure FullCalendar with the CalDAV plugin to connect to a Radicale CalDAV server.
2. Attempt to fetch events from the server.
3. Observe that the request fails with a "400 Bad Request" error.

Expected Behavior

The FullCalendar CalDAV plugin should format dates in a way that is compatible with common CalDAV servers like Radicale, or it should provide a way to configure the date format.

Actual Behavior

The plugin sends dates in the "YYYYMMDDTHHMMSS" format. Radicale seems to expect a different format, leading to a "400 Bad Request" error.

Additional Information

• The problematic code is in the ICAL.Time.fromJSDate(arg.range.start).toICALString() function call, which formats the dates.
• Radicale's logs indicate a "wrong date format" error.
• I am using the plugin via CDN and cannot modify the source code directly.

Potential Solutions or Suggestions

• Adjusting the plugin to use a more universally accepted date format for CalDAV servers, such as the extended format of ISO 8601.
• Or, providing a configuration option in the plugin to specify the date format.