Attachments for events

Is there an option to add an attachments to calendar events? If not, please put it as enhancement.

[georgehrke]

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.

[abditus]

I agree. Attachments would be a great feature. Syncing by CalDAV should include the files.

[georgehrke]

@abditus please refrain from commenting when you can't add anything new. Use Github Reactions instead.

[DavidVentura]

Is this on a roadmap / milestone / anything ? Having link support (like thunderbird) would be enough

[georgehrke]

@DavidVentura I have no intention to implement this soon. There are way more important features missing.

But as always: Pull requests welcome :)

[szaimen]

Any update on this?

[tcitworld]

Was giving a few thoughts to this issue recently.

• 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)?
• 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?

We can probably reuse the files app file picker to make things easier.

@georgehrke @jancborchardt

[georgehrke]

• 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 nextcloud/spreed#1811 (comment)

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.