I'm new to building story maps, and am having trouble building links to web pages on the main stage using the Story Map Journal app. I work at a university and find that, while university web content in our CMS system displays properly, none of our non-CMS web pages appear--the main stage area in the Journal app just displays a loading symbol. Thinking that the pages I'm trying to load might have unsupported HTML, I've tried creating the simplest of test pages with only a line of text and an image and they don't load either--however, I can load the image from such pages if I link directly to the image. Exploring the possibility that there is some kind of security setting with our University's web server that is making trouble, I also loaded the same test web page on a commercial web hosting service, and it didn't load from that source either, though once again I could link directly to my test image.
I'd appreciate suggestions that might address this issue.
Solved! Go to Solution.
Thanks, Stephen and Owen: I've worked it out--it was a security issue, and I had our IT department tweak the security settings so that all the pages I'm trying to install were "https" rather than "http" and that did the trick.
I appreciate your responses!!
John
Are you able to share a public link to your story?
Thanks, Stephen. If you're asking if I've shared my story map publicly, I haven't tried as at this point I'm just testing content to see if I can get what I want playing properly. Are you thinking that even though the pages I'm trying to load don't appear properly in Story Map's edit or preview mode, they may appear properly if I publish the story?
Hi John -- Stephen is asking if you've shared you story publicly so we can troubleshoot your issue. If we can't access your story map we can only guess what might be going on. 😉
It may be that your university website restricts embedding or doesn't support https. If you can share your story we can let you know for sure what's going on and if/how you can fix it.
Owen
Thanks, Stephen and Owen: I've worked it out--it was a security issue, and I had our IT department tweak the security settings so that all the pages I'm trying to install were "https" rather than "http" and that did the trick.
I appreciate your responses!!
John