I used Web Object + HTML with <object> tag to display pdf in a Storyline slide. With that said, I found this cache issue with Review 360 where it will hold on to previous html and pdf of the same names even though they have been updated. For example, I received the "Error loading PDF" warning even though I have updated the HTML to load a new pdf. See the screenshot below. Any advice?
Have you tried loading the course in a different browser? I'm happy to take a look at the file and see what's going on.
You can share the .story file and Rise course link in this discussion. Or if you would prefer to share privately, you can do so by using this link and our Support Engineers will take a look.
Thank you, Lauren. It is really not the browser issue. I used Chrome FYI. What I did is that I changed the folder name, and it worked. This makes me think that Review 360 hold on to "something" on the server-side. Is it possible to check with the engineers? Thanks.
Great call to change the folder name! It's not just a cached issue within Review 360, as I've also seen the same issue within multiple browsers from my days as an ID.
I am having issues as well with PDF. I attached them in resources, and they just won't load. I get a blank screen. I have to manually go into the storyline output and remove the old version that seems corrupted. And then copy the PDF once more.
Is it a certain browser that is not opening the PDF?
Can you share the file with us? You can share it here in this discussion using the "add attachment" button or you can share it privately using this link and our Support Engineers will take a look.
I was having this issue also. The file name of my attachment was quite long. Changing it into Camel Case and shortening the title appear to have worked. Thanks @Marie-Pierre Dionne
11 Replies
Hi Ben!
Have you tried loading the course in a different browser? I'm happy to take a look at the file and see what's going on.
You can share the .story file and Rise course link in this discussion. Or if you would prefer to share privately, you can do so by using this link and our Support Engineers will take a look.
Thank you, Lauren. It is really not the browser issue. I used Chrome FYI. What I did is that I changed the folder name, and it worked. This makes me think that Review 360 hold on to "something" on the server-side. Is it possible to check with the engineers? Thanks.
Hi Ben,
Great call to change the folder name! It's not just a cached issue within Review 360, as I've also seen the same issue within multiple browsers from my days as an ID.
Take a look at this discussion where others have run into the same scenario. And this one here, too.
I am having issues as well with PDF. I attached them in resources, and they just won't load. I get a blank screen. I have to manually go into the storyline output and remove the old version that seems corrupted. And then copy the PDF once more.
Hello Marie-Pierre,
Thanks for reaching out and letting us know that you are running into an issue as well.
We do not support the modification of published output, but I know others have used this approach as well.
PDF on local drive - YES
Viewing like my users - under the resources tab - I get a blank screen.
Hello Marie-Pierre,
Is it a certain browser that is not opening the PDF?
Can you share the file with us? You can share it here in this discussion using the "add attachment" button or you can share it privately using this link and our Support Engineers will take a look.
Thank you Lauren for checking in.
I don't have this issue anymore. I renamed the PDF in camel case and it seem to have done the job.
Before renaming, I was having issues in IE and Google Chrome.
Hi Marie-Pierre,
Thanks for sharing your tip in renaming the file! This will be helpful for anyone else who comes across this discussion.
I was having this issue also. The file name of my attachment was quite long. Changing it into Camel Case and shortening the title appear to have worked. Thanks @Marie-Pierre Dionne
My pleasure! Glad it resolved your issue.
This discussion is closed. You can start a new discussion or contact Articulate Support.