Web Object Issues
While I love the possibility of using WebObjects to extend SL functionality with all sorts of tools (code, documents, etc), I’m running into a few limiting problems. I also want to confirm a few assumptions. Perhaps others could share their knowledge and expertise and let us know if these are known issues. Or maybe there are best-practices, solutions, or other work-arounds for these issues:
- When I right click on the WebObject in Storyline and open it, the url containing WebObject ID (for example: file:///C:/Users/xxx/AppData/Local/Temp/Articulate/Storyline/6CRQ1oF0VLS/zip/6GnVjV3pyK7/index.html) does not match the WebObject ID in the published WebObject folder in story_content. It looks like Articulate creates a temporary number in the “preview”/open mode. Just wondering about this discrepancy. Any insight?
- If I update a file (for example, a js file) that is contained in the folder that I point to when I insert the WebObject and republish, Storyline does not seem to recapture the changes on the edited (js) file. The only way to get Storyline to see the updated file is to delete the WebObject and insert it again. However, that renders a new WebObject ID, which is not ideal when using that number in other places. Is this a known issue? Is there another way to get Storyline to recapture the contents of the WebObject folder without inserting in a whole new WebObject?
- Is it possible to replace a WebObject post-publish? For example, could I replace a pdf in the story_content/WebObjects folder and see the new version in the project? When I tested this, it didn’t seem possible. I'm guessing that SL doesn't actually pull files from this folder at run-time...
- If I publish a SL file with a different name, this also seems to render a new WebObject ID number. Is this also a known issue?