Forum Discussion
AlexDuncan-b8f1
2 months agoCommunity Member
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...
- 2 months ago
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"
MathNotermans-9
30 days agoCommunity Member
I really love these discussions and discoveries as by Jurgen and Nathan. Although tempted to experiment further, i do wait a bit till the new Javascript API is available. As things probably change a lot then ;-)