Open ams-123 opened 4 months ago
Notable implementations to test:
That would be great. But we should first have NextCloud cross the finishing line properly. There are still some quirks to be ironed out. This should also help connecting to other systems.
Thanks. I do see that Gnome 46 now includes CalDAV in its Online Accounts list. Perhaps it makes more sense to integrate via that.
Edit: actually, that's WebDAV, so maybe irrelevant, idk.
I can give baikal account for testing purpose.
I'm using Radicale. An example CalDav url is cloud.kimiblock.top/radicale/kimiblock/random/
where cloud.kimiblock.top/radicale
is radicale's default sub directory and random
being the CalDav location.
(Other clients such as Errands just need cloud.kimiblock.top/radicale
to work)
I'm not sure if another maintainer is already working on it, but I'd love to contribute to this! This is the last thing stopping me from switching to Planify.
Would love to have the fonctionnality
Same here. I use CalDAV as provided by Fastmail. If this article is to be believed, then their backend is Cyrus IMAP. Indeed, when trying to login with the URL specific to my calendar (like https://caldav.fastmail.com/dav/calendars/user/myemail@fastmail.com), I get this error:
<!DOCTYPE html>
<html style='color-scheme:dark light'>
<head>
<title>404 Not Found</title>
</head>
<body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Cyrus-HTTP/3.11.0-alpha0-480-g515a2f54a-fm-20240515.001-g515a2f54 Cyrus-SASL/2.1.27 Lib/XML2.9.10 Jansson/2.14 OpenSSL/1.1.1w Wslay/1.1.1 Zlib/1.2.11 Xapian/1.5.0 LibiCal/3.1 ICU4C/74.2 SQLite/3.34.1 Server at caldav.fastmail.com Port 2075</address>
</body>
</html>
When I used their generic Caldav server address (for clients that support auto-discover of calendars), I get this error:
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
@bennypr0fane see issue from mainstream gnome-online-accounts can help you https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/329
I tried several variations of the provided Fastmail URL's and did not have any luck connecting.
https://caldav.fastmail.com/ https://caldav.fastmail.com/dav/ https://caldav.fastmail.com/dav/calendars/ https://caldav.fastmail.com/dav/calendars/user/ https://caldav.fastmail.com/dav/calendars/user/username@domain.tld/ https://caldav.fastmail.com/dav/calendars/user/username@domain.tld/calendar-specific-string/ https://myfiles.fastmail.com/
I tried creating creating different application passwords for just CalDAV vs the more general CardDAV/CalDAV/WebDAV using Fastmail's UI but neither worked.
I also tried different username strings but no luck username#domain.tld username/domain.tld
I am eager to get this working for my custom domain Fastmail account so would be happy to test any other configurations. Thanks.
Sorry, for now Planify only supports Nextcloud, but we have a plan to support other CalDAV-based services.
Thanks, that's what I guessed. Let us know if/when we can help test other CalDAV-based services.
I just ran into this, because the integrations dialog says "CalDAV" instead of Nextcloud. The modal title is also "CalDAV setup", but then the provider is set to Nextcloud and cannot be changed.
Maybe the first step would be to just call it Nextcloud everywhere, so that users don't expect generic CalDAV to already work.
Is your feature request related to a problem? Please describe. While Planify supports a form of CalDAV, it really only seems to support Nextcloud.
Describe the solution you'd like Actual CalDAV support.
Describe alternatives you've considered Ideally it would not be necessary to run a full-blown Nextcloud instance just to sync tasks.
Additional context Add any other context or screenshots about the feature request here.