I'm currently testing out and learning rise. In an introductory "lesson" we would like to show photos and contact info for staff. I would like to make the staff person's email address be a link that would open the learner's email app. I tried editing the embed link function in rise, but no matter what, it automatically appends "http://" in front of the "mailto:" link. Any help will be appreciated.
Your directions worked for me when I entered "mailto: ahead of the email address and received my shortened email address from http://is.gd. I also took your advice and added the new text block prior to doing the entire process.
It worked fine, the only problem is that I would get ?subject=hello at the end of the pre-populated body text as someone else described above.
I see above that manually entering subject and body is not supported. However, when I went back to JUST entering the email address, the ensuing email is still autopopulating my subject field with "hello" even that is no longer in the mailto code.
I've created a "clean" course to try and replicate this. You can see when you hover over the button, the mailto link that shows up at the bottom of the browser includes ?subject= even though I didn't include that.
I just tried this out and it looks like the default subject line is appearing as expected (it shows the course title). There's not currently a way to change that.
When you click on the link, is that what you're seeing? If not, the quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Could someone help me on this soon please? I have to publish a programme and I need to know soon if this is possible or what I am doing wrong. I followed the steps published here https://360.articulate.com/review/content/384708bb-cab7-4ed9-9597-0aa91a65232b/review and the button is just dead. Is there a missing step - what is going on? Is it only operational when published and not in Rise preview? Please respond.
Hi, Jennifer! I just double-checked using the steps in this document and was able to test a button block email link in preview mode.
Check your procedure against that document and, if you're still not seeing the expected results, submit a case here so that our Support Team can take a look.
Hope that helps! Let me know if there's anything else I can do for you.
How, in an over two year old thread, has this functionality not been fixed yet. For all that Rise brings in the WYSIWYG realm, some of the basic functionalities point to a disturbing lack of awareness.
No header/footer across the entire course, no use of "mailto", no closed captioning options on videos, etc.
I totally get that you're frustrated. I thought it may be helpful if I provided some more insight into how we handle feature requests.
First of all, it may be helpful for you to know that we receive hundreds of feature requests every week. As you can imagine, prioritizing such a large number of feature requests is no small task and we take it very seriously. Here's an inside look at how that process works.
Please know that we're doing our very best to bring our users the features they want and need as quickly as possible.
Are the roadmaps or feature request lists ever published? I would love to know where this, and other issues, stand at a given point in time. The Articulate community is so helpful and this would be a big win for transparency.
Hi there, Greg. We don't have a published version of our roadmap, but as we get closer to features we know we'll release, we'll let you know. I know it's important to plan what to expect as you're authoring.
We are still tracking the request for in-text mailto: functionality. Right now, we don't have an ETA on any additional support beyond the button blocks, but we'll let you know if that changes!
Oh this is such an oversight, please fix it! I agree with the people who said this should not be considered a feature request because it's clearly a design flaw if you are hesitant to call it a bug.
Since this is a long time request and in terms of design, an inline embedded code is more seamless than the rigid layout with the button with almost no customisation.
Also I tried to add a mailto tag in the course description where no button is available ..
There isn't a way to add a mailto: link or a button in the course description area. I'll let our team know you have a need for that.
You can hide the course sidebar and the previous/next buttons in the Settings area. Under the Navigation tab, select No Sidebar, and set the previous and next buttons to Off.
Currently mailto: links aren't supported in the text hyperlink feature. If we add mailto: functionality in the future, we'll let you know!
I was referring to the controls of the video (Play/Pause volume and progression bar/slider ...) but since we don't have the autoplay yet, it makes sense to have them there. :o)
If I write an email and press enter - it is automatically conveted to a hyperlink with an "http://" added before "mailto" and clicking it produces an error. I add to the comment above - could you please remove the automatically added substring "http" to mailto so that the mailto: could work? Many thanks!
85 Replies
You're welcome! :)
Thank you, John!
Your directions worked for me when I entered "mailto: ahead of the email address and received my shortened email address from http://is.gd. I also took your advice and added the new text block prior to doing the entire process.
Thank again!
Linda
This post was removed by the author
This post was removed by the author
I've been using the button feature but I'm seeing some odd behaviour.
I was trying to add mailto: code that would also populate the subject and body,
eg, mailto:person@email.com?subject=hello&body=This is some text.
It worked fine, the only problem is that I would get ?subject=hello at the end of the pre-populated body text as someone else described above.
I see above that manually entering subject and body is not supported. However, when I went back to JUST entering the email address, the ensuing email is still autopopulating my subject field with "hello" even that is no longer in the mailto code.
I've created a "clean" course to try and replicate this. You can see when you hover over the button, the mailto link that shows up at the bottom of the browser includes ?subject= even though I didn't include that.
Any ideas???
Hi Christina,
I just tried this out and it looks like the default subject line is appearing as expected (it shows the course title). There's not currently a way to change that.
When you click on the link, is that what you're seeing? If not, the quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Am I doing something wrong? I added the button but when I preview it doesn;t seem to work at all.
Could someone help me on this soon please? I have to publish a programme and I need to know soon if this is possible or what I am doing wrong. I followed the steps published here https://360.articulate.com/review/content/384708bb-cab7-4ed9-9597-0aa91a65232b/review and the button is just dead. Is there a missing step - what is going on? Is it only operational when published and not in Rise preview? Please respond.
Hi, Jennifer! I just double-checked using the steps in this document and was able to test a button block email link in preview mode.
Check your procedure against that document and, if you're still not seeing the expected results, submit a case here so that our Support Team can take a look.
Hope that helps! Let me know if there's anything else I can do for you.
How, in an over two year old thread, has this functionality not been fixed yet. For all that Rise brings in the WYSIWYG realm, some of the basic functionalities point to a disturbing lack of awareness.
No header/footer across the entire course, no use of "mailto", no closed captioning options on videos, etc.
Hi Rob,
I totally get that you're frustrated. I thought it may be helpful if I provided some more insight into how we handle feature requests.
First of all, it may be helpful for you to know that we receive hundreds of feature requests every week. As you can imagine, prioritizing such a large number of feature requests is no small task and we take it very seriously. Here's an inside look at how that process works.
Please know that we're doing our very best to bring our users the features they want and need as quickly as possible.
Let me know if you have any other questions!
Are the roadmaps or feature request lists ever published? I would love to know where this, and other issues, stand at a given point in time. The Articulate community is so helpful and this would be a big win for transparency.
Well, It's been a year since this has been posted and no change.
Hi there, Greg. We don't have a published version of our roadmap, but as we get closer to features we know we'll release, we'll let you know. I know it's important to plan what to expect as you're authoring.
We are still tracking the request for in-text mailto: functionality. Right now, we don't have an ETA on any additional support beyond the button blocks, but we'll let you know if that changes!
Fab tip, saved me much angst, thanks!
Is there any update in the mailto feature? We are trying to add it to a course now and wondering if there is an easy way to do this now.
Hey Melissa!
It sounds like you want to hyperlink text with a mailto: link, is that right?
Thanks for adding your voice to that feature request! For now, you can hyperlink a button block with a Send an email destination.
We'll let you know if we add this feature to text blocks in the future!
Oh this is such an oversight, please fix it! I agree with the people who said this should not be considered a feature request because it's clearly a design flaw if you are hesitant to call it a bug.
The last post is dated "over a year ago".
Would you have an update on the mailto: request?
Also http:// is fading out, at least should Rise adds https:// if it had to instead?
Hi Thierry!
Right now, you can hyperlink a button block with a Send an email destination.
Can you tell me more about your need for Rise to add
https://? Do you have an example where the hyperlink is not working correctly?Thank you Alyssa.
Since this is a long time request and in terms of design, an inline embedded code is more seamless than the rigid layout with the button with almost no customisation.
Also I tried to add a mailto tag in the course description where no button is available ..
A quick example here:
https://rise.articulate.com/share/CttA6K_LhVw0bLiLiWD0Wl2dMutjV6gi
On a side note, the auto play feature discussed elsewhere would be welcome here to play the video on entering the slide/page.
I also tried to hide the player control and slider but it doesn't seem to work.
Why does Rise add http:// when you embed a link/mailto?
...
Great questions, Thierry!
Thank you Alyssa. Love your work.
I was referring to the controls of the video (Play/Pause volume and progression bar/slider ...) but since we don't have the autoplay yet, it makes sense to have them there. :o)
Thanks for the tips.
If I write an email and press enter - it is automatically conveted to a hyperlink with an "http://" added before "mailto" and clicking it produces an error.
I add to the comment above - could you please remove the automatically added substring "http" to mailto so that the mailto: could work?
Many thanks!