-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 link share email template through APIs #29937
Comments
Also not discussed so far: email subject ? |
The email endpoint could potentially be abused to send non-share-related emails to anyone... I don't like this. We could force it to have at least the share id, but still... |
No, this feature is not really about sending invitation emails. When adding a recipient I'd expect the share id of the original share to be specified. |
For "1. Public API endpoint to retrieve…" subject should be retrieved from oC server too. If I share a link with my mobile mail client, subject will be used. If I share a link with a messaging application, only the body will be used. |
@michaelstingl good point. Indeed mobile will use the local mail client, so the subject should be available too.
|
Could be used to solve owncloud/client#6196 |
Duplicates Hackweek's #29769 maybe? |
For #29935 I would also be happy with just "injecting" a note to the notification mail. Not 100% sure if users want to edit the whole template there or if oC should just provide an option to insert a personal note to an existing template (and templates can be edited elsewhere, e.g. templateeditor). |
moving to planned |
We don't need to make the full template editable but the API should be capable of injecting a personal note as in the WebUI #29696. |
moving to triage. personal note is implemented in 10.0.8 |
Provide a way for clients to retrieve the email template through public APIs.
Public API endpoint to retrieve preformatted email template with filename, expiration date as input
Public API endpoint to send out email with body (tech debt from ajax/share.php which needs to be moved anyway, see Sharing 2.0 internals #22209)
This is a follow up of #29935.
I suggest providing a new OCS Share API endpoint for that.
Note that only plain text messages are supported. Not sure if we should support HTML emails as it would require clients and web UI to provide basic formatting.
@michaelstingl @felixheidecke @pmaier1
The text was updated successfully, but these errors were encountered: