Forum Discussion
hashed filenames in published output
Problem: when storyline files are published, media filenames are replaced with hashed filenames in the published output (a 11-character series of apparently random alphanumerics). We have a search to...
if you are really precise, the filename is not a hash - it is independent of the content.
It is generated when the medium is imported - a GUID-4 is generated, e.g.
- "06a3dc93-48e9-4ac5-97d2-cec1cd3df540"
- the guid is then split into its 5 blocks
- the last two blocks are removed
- the first three are put together backwards
- the whole thing is now converted to base62
- at the end, an “R” is added in front and the appropriate file extension is added
- result: "R5wlhTmswUhH.png"
if you now parse “story/story.xml” in the .story file, you can find out the mapping between the original file name and the generated file name
- "06a3dc93-48e9-4ac5-97d2-cec1cd3df540"
Jurgen - thanks for your response. I'm looking at a .story file, and I've found a filename for one of my graphics that's been converted (with the "R" added, as you indicated). However, all of the text around it is nonsense to me. I see nothing that looks like a GUID. For example, the text immediately following is "¢ ( lWUP l\4¸Ëâîîîî‹XÜ-¸;,î¶Ü5¸Cðஂ† Á‚Ûý÷xU÷ðUWMOÍÃ753Ýqšê".
There's some aspect of your instruction above that I'm not following. Can you clarify a bit? In particular, where should I find the GUID relative to the filename in the .story file?
