PDF filename changes when downloading from Rise

Hi there,

We have noticed that when downloading a pdf document (from the pdf multimedia block) the filename of the downloaded document is different than the filename of the document when it is in Rise.  See attachment for screenshots.  Is this supposed to happen?  If so, what is the rationale in changing the filename?  We would really appreciate it, if someone can shed some light on this for us.  Thank in advance and have a wonderful day!

88 Replies
Alyssa Gomez

Hi there Amber! 

I've seen this, as well. It looks like it also happens with other file downloads, like PNG files. I'm not totally certain on the rationale behind the extra characters added to the file name, so I've reached out to my team for their expertise. In the meantime, is this causing issues for your learners? 

David Martinez

Hey Alyssa! Just ran across this post and we seem to be having the same problem.  This is our first Rise course being uploaded on to our LMS. See the attached image - this error is for an actual stock photo in Rise from the library - seems that Rise added extra characters and now the image path is too long. Any suggestions? 

Ashley Terwilliger

Hi Matthew and Jackie! 

Sorry you're both having trouble with this too. 😕 

Matthew, I don't have an update on when/if yet - but as soon as we do we'll post here in the ELH discussion so you'll get an email notification if you're subscribed. 

Jackie, What error message are you getting? The one about an invalid embed code? Take a look at the troubleshooting steps here. 

Jason Lane

Hello, I'm looking for a solution here as well. We name uploaded multimedia files (PDFs) withn an alphanumeric naming policy to help learners build a library of take-away resources. The unique characters (e.g. JlQomjxZb7rOw3nc_GxfIiesleN1h7Qyz-booklet-1-job-options.pdf) is an issue as it makes it difficult for learners to organise the downloaded resources in the course. I have subscribed to this thread pending any updates.

Thanks,

Jason

Allison LaMotte

Hello again Cheng,

I looked into this further and it seems like it's an issue specific to Internet Explorer 11. It works fine in Firefox, Chrome, and Microsft Edge.

I'm logging a bug for this. Thanks for bringing it to our attention. :) 

I'll let you know via this thread when any updates are available.