I just uploaded storyline 360 course but one of my pdf external files doesn't load. The message i get is "This XML file does not appear to have any style information associated with it. The document tree is shown below."
Its been quite frustrating because Ive been try almost everything.
Someone there who can help me with this issue please!
It appears to be a problem with the location of the pdf. I have gotten a similar message from S3 if I forget to set the folder to pubic access. If I am reading the URL correctly, it appears that the pdf is not in the same spot as the project. that could be caused by linking to it instead of putting it in resources. A file in resources is packaged during publishing. That means it is copied, and uploaded as part of the project. If it is just a link, the published destination may not have access to the original.
Of course, I'm just guessing. Someone who can see the .story file may be able to give you a better answer. Attach it here, and see what you get.
I had this same problem when I uploaded a .PDF to the resources section of my Storyline 360 project, created a button trigger to open it using story_content/external_files/(file name).pdf, but did not immediately save the entire project before publishing it. After publishing to Review 360, I got the XML file error message above. Upon reopening the Storyline project file, I found the document was no longer in the resources section. Uploading the .PDF to resources, saving and closing resources, and then immediately saving the entire Storyline project before publishing solved the problem.
2 Replies
It appears to be a problem with the location of the pdf. I have gotten a similar message from S3 if I forget to set the folder to pubic access. If I am reading the URL correctly, it appears that the pdf is not in the same spot as the project. that could be caused by linking to it instead of putting it in resources. A file in resources is packaged during publishing. That means it is copied, and uploaded as part of the project. If it is just a link, the published destination may not have access to the original.
Of course, I'm just guessing. Someone who can see the .story file may be able to give you a better answer. Attach it here, and see what you get.
I had this same problem when I uploaded a .PDF to the resources section of my Storyline 360 project, created a button trigger to open it using story_content/external_files/(file name).pdf, but did not immediately save the entire project before publishing it. After publishing to Review 360, I got the XML file error message above. Upon reopening the Storyline project file, I found the document was no longer in the resources section. Uploading the .PDF to resources, saving and closing resources, and then immediately saving the entire Storyline project before publishing solved the problem.