Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose subscribed webcal calendars via CalDAV #26193

Closed
grafenhofer opened this issue Sep 23, 2016 · 19 comments
Closed

Expose subscribed webcal calendars via CalDAV #26193

grafenhofer opened this issue Sep 23, 2016 · 19 comments

Comments

@grafenhofer
Copy link

grafenhofer commented Sep 23, 2016

The calendar app has recently gained support for subscribing to third party webcal calendars (see owncloud/calendar#132). It would be great to expose these imported calendars via CalDAV (e.g. to mobile clients). Nextcloud would act as a kind of proxy service. One usecase is increased privacy for (mobile) users (only the Nextcloud server connection gets exposed to the original webcal provider).

Related nextcloud issue: nextcloud/server#1497

@Pazu
Copy link

Pazu commented Nov 5, 2016

See also my new commentary on owncloud/calendar#751. This appears already to work using CalDAV-Sync, but not other clients. It would be interesting to find out why.

@ghost
Copy link

ghost commented Nov 6, 2016

Comment from owncloud/calendar#751 (comment)

This is an issue that you need to bring on the clients that you use.

@Pazu
Copy link

Pazu commented Nov 6, 2016

Very well, @RealRancor. In that case, completely disregard everything I said and treat it as a feature request. I'll delete all my comments tomorrow.

@ghost
Copy link

ghost commented Nov 6, 2016

@Pazu As it seems its not clear to you what that comment means:

I think @tcitworld tried to say there that you should contact the author of your used android/ios app and report a bug to them that they seems to have an issue in their app.

@Pazu
Copy link

Pazu commented Nov 6, 2016

@RealRancor: the Android app exposes subscribed calendars via CalDAV, which is what we want. Whether or not the client is doing something right or something wrong is unknown to me.

Apple's Calendar application doesn't expose subscribed calendars via CalDAV. Whether or not it's doing something right or wrong is unknown to me.

I will not contact Apple and report this behavior as a bug.

I'll delete my comments tomorrow.

@ghost
Copy link

ghost commented Nov 6, 2016

Whether or not the client is doing something right or something wrong is unknown to me.

Thats why you get the info like the posted comment above where the issue is coming from.

I'll delete my comments tomorrow.

No need to delete comments.

@Pazu
Copy link

Pazu commented Nov 21, 2016

I think I solved this. In Apple's Calendar application, I needed to update the server path from the old style to the new (that is, the one currently shown by ownCloud 9.1.2 as the "iOS/OS X CalDAV address"; e.g., "https://example.com/remote.php/dav/principals/users/USERNAME/"), and the subscribed calendars suddenly appeared.

@martinlanger90
Copy link

In DAVDroid they're not shown anyway.
But this should be DAVDroid bug then? Am I right?
Thanks

@Pazu
Copy link

Pazu commented Nov 21, 2016

@martinlanger90 With which exact URL style did you add the ownCloud account to DAVDroid?

(With CalDAV-Sync, for example, it's only necessary to use the minimal 'https://example.com/' style and it seems to find the correct DAV point.)

@martinlanger90
Copy link

martinlanger90 commented Nov 21, 2016

Yep. Tried with minimal url and tried with your extended one above my post. Both don't show up the subscribed calendars. Maybe I can collect a log from DAVDroid. But I've to figure out how to take logs with DAVDroid first. And yes with CalDAV-Sync it works. But unfortunately not with DAVDroid which could sync contacts as well.... Thank you anyway

@ghost
Copy link

ghost commented Nov 21, 2016

But I've to figure out how to take logs with DAVDroid first.

There is a longer FAQ available here explaining the needed steps: https://davdroid.bitfire.at/faq/entry/how-to-debug/

@martinlanger90
Copy link

martinlanger90 commented Nov 21, 2016

Got some information on that already. So it seems, DAVDroid can't handle this, until the subscriptions aren't exposed via CalDAV.

https://forums.bitfire.at/topic/1210/nextcloud-calendar-subscription-not-shown/3

and that:
nextcloud/calendar#63

@PVince81 PVince81 added this to the backlog milestone Jan 27, 2017
@brianjmurrell
Copy link

The https://example.com/remote.php/dav/principals/users/USERNAME/ format URL doesn't work on Evolution to show subscribed calendars, just the local ones.

@samweisgamdschie
Copy link

Hi! do you have any news at this topic? to publish all subscribed calendars over caldav would be very awesome, because with this feature it would be possible to easily centralize a next part of my daily life into nexcloud! 👍

@Pazu
Copy link

Pazu commented Mar 14, 2017

The news is that it works if you use the correct CalDAV URL, but not with some CalDAV clients, notably DAVDroid.

@ghost
Copy link

ghost commented Mar 14, 2017

@samweisgamdschie If you're running nextcloud you're mostly wrong in this issue tracker. Try it in the nextcloud issue tracker if you want news for nextcloud on this topic.

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.

@brianjmurrell
Copy link

It doesn't really seem appropriate that an issue is closed because it is waiting for activity from the owncloud team but then the owncloud team doesn't take any action and instead just closes the issue.

Feel free to reopen this issue if you deem it appropriate.

I don't seem to have any ability to do that.

@lock
Copy link

lock bot commented Jul 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants