Forum Discussion
Publishing without Flash using multiple tracking options - bug
Yep! Here was my original documentation which included console errors:
"I have tried this tutorial and the original print to html tutorial and I can't figure out why my variables are not passing (or maybe they aren't storing). I have added the files to linters and combed the code side-by-side without any troubleshooting luck or obvious issues.
Only one DOM error on client-side in my code files:
Uncaught DOMException: Blocked a frame with origin "null" from accessing a cross-origin frame.
at file:/process.js:4:32
Line 4 referenced: var player = opener?opener.top.GetPlayer():{} ;
I then took your "pretty" story file and published with my code files and your example story file doesn't pass the variables when launching print.html. Next, I took your code files and published my story file and had the same result: now my story file doesn't pass variables even using your code. I tried using a newer version of Jquery, and ensured that the story file was updated to 360 format."
The JS error is preventing the user.is from running it is a cross domain issue.
Are you running it from inside review? As review opens it from inside an iframe it may not be visible.
Sent from my iPhone
No, I have been publishing to desktop and running direct in browser while testing.
You need to upload the JavaScript is unlikely to work locally
Sent from my iPhone
Hmm ok, JS runs just fine in Chrome browsers. I am unaware of a case where it wouldn't work in a Chrome/Edge browser. I will try your solution.
I am still curious about why js variables are not passing when content is published in SL 360?