-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Unable to add parameters to mailto links #5950
Comments
Hi @phette23 - thanks for the suggestion. A potential issue with having users enter mailto: links is that editor-level users are not necessarily technical, and may not know how to construct them. I think the way forward would be to have a separate optional field for subject / cc in the link chooser, which would then store the link internally as something like |
PR raised a while ago with a partial solution - would be good if anyone is keen to pick that up and redo on the latest code + fix one of the minor feedback items. |
Closes wagtail#5950 Rework of PR wagtail#6451
#10920 has implemented the subject/body request in this issue, we will close when merged. If support for cc/bcc is still requested, that can be requested as a future enhancement issue, it will likely involve a bit of InlinePanel to allow for multiple adding/re-ordering of a CC and/or BCC address. |
Issue Summary
Using the rich text editor, you cannot add additional URI parameters to a
mailto
link such as subject, bcc, cc, etc. You can only pass a single email address.Steps to Reproduce
help@example.com?subject=Help+Me
orhelp@example.com?cc=support@example.com
I think the solution could be to validate not against an email address, but a mailto URI. I looked at the Draftail repo first but decided to open the issue here, since it seems that the link selection dialog is native to Wagtail and not the editor itself; forgive me if I'm wrong about that.
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
No, but we are on the latest release (2.8).
Technical details
The text was updated successfully, but these errors were encountered: