I added a couple of links to pdf documents using click boxes, link to file. When I publish using Flash Player 10, I am able to open files from the htm file that is published to my C:\. When the files (zip) is uploaded to SABA LMS the links don't work. I can see the hand cursor when I bring mouse to the click area, but nothing happens when I click it.
Files are currently stored in a network drive. Link is pointing to their respective path in the network drive. I suspected it had to do with file location and added files to the zip file before uploading to LMS but the URL is still pointing to the shared drive. LMS administrator does not know of a path assigned by LMS that I could change my URL to. What URL should I use? Or is there another solution to my problem?
Thanks in advance for your input!
I think I'd begin troubleshooting this by first creating a link to something like Google.com. Push the project to your LMS and test that first. If it fails to work, you know you have some sort of issue to address with the LMS and the manner in which it is serving the content.
Assuming the link works fine, the next step would be to ensure you are using an absolute URL to the PDF in question. For example: http://www.somesite.com/somefile.pdf.
Helpful and Handy Links
I've tested with other URL to the intranet and it worked fine. The files are not currently assigned an absolute URL as you suggest would be the solution. To confirm, does that mean that a path to files on the network will not work?
The only way an absolute path on the network will work is if anyone accessing the project sees the path in the same way. For example, you might see it as F:\SomeFolder\SomeFile.PDF. But if they see it as G:\SomeFile.PDF this will not work of course.
You might be able to code it as \\ServerName\FolderName\FileName.PDF.
Helpful and Handy Links
Hi, Ive just found this post by searching as I have a similar problem.
Im tring to add a button that points to a shared folder that contains a PDF but it (the PDF file) regularly gets updated so I didnt just want to import the PDF, otherwise I'd have to update the captivate course every time. (does that make sense?)
I thought by adding the absolute URL (meaning the full network URL??) it would solve the problem Im having and I got really excited (as Ive been trying to solve the problem for hours) when I didnt get an error (below) when I published the file. But when I have uploaded it onto the LMS the problem is still there. The hand cursor shows over the link but nothing happens when I click.
The message Im getting when I publish is:
The files.projects listed below are linked to the open project. The linked files/projects may need exporting.
[R:\Business Support\SRM\training materials\Quick Guides\Siebel Quick Guide v1.1.pdf(text & Image1)
It is also important to copy all referenced files and projects with their corresponding HTML files to the output folder.
I tried to add the \\crwin.crnet.org\dfs\bus\dept\ infront of the R: which I thought would point the user to the correct location, but the link still isnt working.
Please can you advise?
If your PDF is sitting in a folder on a LAN drive then ALL of your users would need to add that LAN drive folder location as a trusted location in their Flash Global Security settings in order for that link to work for them.
Even though the Captivate SWF and HTM page that launches it are being served up from a web server over HTTP, you're still running into the Flash Global Security issue because you're trying to access a file on the LAN.
Since it's generally impractical to try to get all users to start configuring their Flash Global Security settings, the best solution is to move that PDF onto the web server too. Then your link should work. Try it as a test.
Hopefully Rod won't mind me adding the following bit.
I think Rod's advise is excellent. The only bit I would add is that if you choose this path, all you need to do is ensure you type the PDF file name and don't worry about any pathing. Just make sure the PDF is inside the same folder as the captivate and you should be good to go.
Helpful and Handy Links
Rick's suggestion is also quite correct. Another thing worth mentioning is that it's always best practice to use all lower case for published folder and filenames. This avoids potential linking issues with some web servers that are UNIX or LINUX based.
Also NEVER have spaces in your names as this will break links once content is published to the web.
Hi, thanks for your advice, though Ive decided the easiest option is to just state the path users need to follow to find the document for themselves. Im not sure how to follow your instructions above as I dont understand some of the terminology.
I now have another problem with text from pervious slides showing on my quiz slides, Im so frustrated right now! (Ive just posted this problem in response to someone having the same issue so hoping I get some advice to resolve it)
Hi Rod, I am facing a similar issue with my project. In my project I have inserted a button. Clicking the button users should be able to open or save a PDF file.
I tried placing a link to the file and then including the PDF in the publish output folder. It works fine from my system, but fails when published on our Webserver. Then I had the file hosted on our webserver, placed the URL in the button properties. The file opens successfully in the preview mode, but fails on publishing. I see the hand cursor while hovering over the button, but the desired action fails. My URL has the following pattern http://sims.companyname.com/GetDocument.aspx?docid=1234. I am not sure if I have missed anything in the button configuration. I tested with other urls such as google.com. Works fine in the preview mode, but not when published. Please advise.
Just checking a detail here: When you say your content is publsihed "on our Webserver", are you certain you are NOT referring to a LAN server? Is the link to access your Captivate HTM on that server starting with HTTP:// or is it starting with a drive letter or something like this //servername/foldername/captivatefilename.htm?
Europe, Middle East and Africa