Is there an option to add an attachments to calendar events? If not, please put it as enhancement.
There is a $5 open bounty on this issue. Add to the bounty at Bountysource.
Other CalDAV clients like thunderbird can already add attachments. The web calendar can't. Definitely something we should consider for the future.
Instead of writing the attachment into the actual calendar data I would suggest to upload it to the nextcloud and just link there.
I agree. Attachments would be a great feature. Syncing by CalDAV should include the files.
@abditus please refrain from commenting when you can't add anything new. Use Github Reactions instead.
Is this on a roadmap / milestone / anything ? Having link support (like thunderbird) would be enough
@DavidVentura I have no intention to implement this soon. There are way more important features missing.
But as always: Pull requests welcome :)
Any update on this?
Was giving a few thoughts to this issue recently.
.calendar-attachments hidden folder)?We can probably reuse the files app file picker to make things easier.
@georgehrke @jancborchardt
- Should the editor offer the possibility to pick an existing file?
- When uploading a new file, should the editor let the user pick where to upload the file (or to a fixed .calendar-attachments hidden folder)?
As a first iteration of implementing attachments, i would not allow uploading new documents at all. Only picking existing files from Nextcloud for now.
Later on we can add the possibility to upload new files. There is a related discussion going on in Talk right now, see https://github.com/nextcloud/spreed/issues/1811#issuecomment-505096933
Since the event may be shared/exported to people without access to the file, should the link to the file always be a public link? Or do we add a « public link » checkbox/toggle?
I think the link should always be public, but I'm not sure if we need a new share-type for that in the server. This can be a bit tricky. Even when you remove the attachment from a desktop or mobile client, the public link should automatically be unshared.
No matter what we do, if we automatically make the file public, we need some code changes in the server to detect if the attachment has been removed again.
So for now i would say just include the internal https://nextcloud.local/f/666666 link and find a proper solution for public attachments for Nextcloud 18.
Since I don't know whether attachments can be based on the caldav standard, I think the best option would be to automatically write the internal link of the attached file into the description-field. Otherwise you probably get problems with some calendar client apps.
But these attachments should when directly uploaded or chosen from the computer to get uploaded be located in the appdata folder as suggested here: https://github.com/nextcloud/spreed/issues/1811#issuecomment-505096933 and the internal link of this file then also automatically peopagated onto the decription field imo.
Also I am not sure about automatically making all these attachments publicly accessible. So the internal link is more appropriate imho.
Maybe when sharing the calendar event with a nextcloud user, an internal link for this user could be created (and automatically pasted into the description field) and when sharing the event with a mailaddress or over a link, also a public link to this file should be created (and also automatically pasted into the description field). The same could apply to sharing whole calendars.
BTW: maybe you can also use the viewer app to show these attached files directly in the calendar app since https://github.com/nextcloud/viewer/pull/271 is merged? :)
I didn't follow the developement up to this point, so please disregard my posting if it has already been taken care of:
Reading something about internal links I wonder if regular calendar apps like the one from Thunderbird will work in a way the user is used to handle calendar attachements. To me this seems a very important requirement for acceptance of this solution within the users.
- When uploading a new file, should the editor let the user pick where to upload the file (or to a fixed .calendar-attachments hidden folder)?
As a first iteration of implementing attachments, i would not allow uploading new documents at all. Only picking existing files from Nextcloud for now.
Yep, good call. And similar as in Talk, once we do allow uploading files, for those there should indeed be a fixed hidden folder.
As a first iteration - why not. But just keep in mind this will lead to a different behavior when you use the calendar in Nextcloud compared when you use it on your phone / Lightning / etc.
Thunderbird lightning does not allow you to add attachments as files, only as links (Thank god for that)

So that would be exactly the same behaviour as in Nextcloud, just that we show a file-picker for Nextcloud and add the link to the file, instead of allowing to add arbitrary web links.
So if you add a file in Nextcloud, it would show up as https://nextcloud.tld/f/777772 in Thunderbird and if you click it, you will have to log in.
Edited my original text, having read @georgehrke 's opinion on this in an older support thread: https://help.nextcloud.com/t/idea-app-for-organizing-partys-meetings-events/6486/4
My original comment was indeed more a Resources thing than pure attachments.
Related: https://github.com/nextcloud/calendar/issues/2415
If an image is selected, it should replace the automatically generated event image in details view.
Or even: Always show a file preview (if available) instead of the automatically generated event image in details view.
Multiple files attached? only show one preview
We too would like to have attachments for calendar events. Attachment can come from nextcloud user files. To make user's life simpler, a simple "select file or upload new file" should be added to the calendar event editor. And share permission on the just uploaded/shared file should be copied from shared permission of the calendar.
Most helpful comment
Thunderbird lightning does not allow you to add attachments as files, only as links (Thank god for that)
So that would be exactly the same behaviour as in Nextcloud, just that we show a file-picker for Nextcloud and add the link to the file, instead of allowing to add arbitrary web links.
So if you add a file in Nextcloud, it would show up as https://nextcloud.tld/f/777772 in Thunderbird and if you click it, you will have to log in.