Create a new webpage (something simple) published as HTML and only containing a hyperlink to your PDF file in SharePoint, then upload it to SharePoint.
Publish it to SharePoint the same way you published your SL project.
Try the link when viewing the site and see if you still have the problem.
If you still have the problem, contact your IT to resolve it because it may be security rights related.
This will isolate Storyline from the issue and confirm that SharePoint is the issue.
If the test above works, then you can directly launch the PDF in SharePoint and collect that URL to compare to your Storyline URL in use.
i did some researching and it seems that sharepoint restrictions include file and folder names ending in "_files", etc.
While bulk importing content from the file system (e.g. images) via the PRIME API, I found out that SharePoint does not allow folders that end in “.files” or “_files” (which my customer just happens to have). This is apparently aknown issue (at least as early as 2008-06-28).
I have initiated a change request to correct KB 905231, as follows.
In addition, file and folder names cannot end with:
.files
_files
-Dateien
_fichiers
_bestanden
_file
_archivos
-filer
_tiedostot
_pliki
_soubory
_elemei
_ficheiros
_arquivos
_dosyalar
_datoteke
_fitxers
_failid
_fails
_bylos
_fajlovi
_fitxategiak
unfortunately, there is a folder in the publishing SL course called "external_files"; it contains all the linked pdf files. this is causing the problem when launching the hyperlinked files. it is a known issue with sharepoint.
is there a way to rename the "external_files" folder once it is published so it will not have this problem when publishing to sharepoint?
I know of no way to remane the folder and reconfigure a story to use the path. I beleive the path is hard-coded because I see no reference in any js or xml file.
You could open a ticket with Articulate, however, your change request with SP would most likely be a faster resolution.
3 Replies
Hi Ceasar:
Do a little test:
Create a new webpage (something simple) published as HTML and only containing a hyperlink to your PDF file in SharePoint, then upload it to SharePoint.
Publish it to SharePoint the same way you published your SL project.
Try the link when viewing the site and see if you still have the problem.
If you still have the problem, contact your IT to resolve it because it may be security rights related.
This will isolate Storyline from the issue and confirm that SharePoint is the issue.
If the test above works, then you can directly launch the PDF in SharePoint and collect that URL to compare to your Storyline URL in use.
I hope this helps.
Best Regards,
Dennis Hall
thank you for the reply dennis.
i did some researching and it seems that sharepoint restrictions include file and folder names ending in "_files", etc.
While bulk importing content from the file system (e.g. images) via the PRIME API, I found out that SharePoint does not allow folders that end in “.files” or “_files” (which my customer just happens to have). This is apparently aknown issue (at least as early as 2008-06-28).
I have initiated a change request to correct KB 905231, as follows.
In addition, file and folder names cannot end with:
unfortunately, there is a folder in the publishing SL course called "external_files"; it contains all the linked pdf files. this is causing the problem when launching the hyperlinked files. it is a known issue with sharepoint.
is there a way to rename the "external_files" folder once it is published so it will not have this problem when publishing to sharepoint?
Hi Ceasar:
I know of no way to remane the folder and reconfigure a story to use the path. I beleive the path is hard-coded because I see no reference in any js or xml file.
You could open a ticket with Articulate, however, your change request with SP would most likely be a faster resolution.
Good Luck,
Dennis Hall
This discussion is closed. You can start a new discussion or contact Articulate Support.