Forum Discussion
Big Red X in Story View
When I select "Story View" to view scenes, a big red X appears. I have been working for about 6 hours in slide view and wanted to view the aggregate. Why did the red X appear and how do I get rid of it? I'm working on Articulate 360. Thanks!
47 Replies
Hi Bruce,
If you're already working locally when making changes to your project file, try doing a repair of your Storyline 360 installation to see if this helps. If the issue persists, you can reach out to our support team by opening a case so we can take a closer look what's happening.
- JaneMullooly-e5Community Member
Big Red X - Potential Solution
With the help of Lianne on the Articulate Support Team, the solution I found was to check for unicode text using this link: https://freetools.textmagic.com/
I found that, when I copied and pasted text from the slides into the Notes section, a big red X appeared that then transposed itself to all of the slides into the project, rendering it impossible to publish. The solution was to:
a) make a note of the slide it happened on and copy the text from the problematic slide
b) paste the text into 'textmagic.com' to find out where the unicode was appearing
c) copy the entire project and save it with a new name
d) open the new project
e) delete the offending slide
f) recreate the slide while being careful to avoid unicode text. The text book solution to the unicode text problem is to copy and paste in Notepad to wipe the unicode text out. However, I found that the unicode still appeared in paragraph breaks, so I just used separate text boxes in the new slide to denote paragraphs.
e) Save and republish
It has taken me over three days to figure all this out, after importing into a new project/uninstalling and reinstalling the software etc. etc. Hopefully, this post will save someone out there a lot of time and unnecessary angst.
Jane
- Jürgen_Schoene_Community Member
do you have such a "dangerous" text, or a link to "dangerous" text on the web
then could be tested, what really goes wrong in storylineUPDATE: or better upload a small .story file with such an "dangerous" text
- brucefrenchCommunity Member
- EricLoopCommunity Member
Greetings. First-time poster here.
I'm also encountering the X error message. It first occurred in Slide Master EDIT STATE. It now appears on all slides, when a Storyline icon is selected in Edit State. The selection of other objects (text boxes, images) in Edit State also now throw the error. As you see in the .png, I had made 3 states for the icon, but at some point, if any other icon is selected, it too comes up with the error.
I've checked others' issues and:
- Unicode Text (none)
- Modern Text (no option to 'turn off')
Storyline version: v3.73.29904.0
Mac environment running Parallels 10 and Windows 11
There doesn't seem to be a solution for this other than deleting the offending slides/icons and starting again. Of course, I'd rather not do that...
- JohnMorgan-c50cFormer Staff
Hi Eric,
Wow! Let's see how we can fix this big red X situation and help get you back on the right path.
- Are you working from a network or shared drive? Always save and publish Storyline projects on your local hard drive (typically your C: drive). Working on a network drive or an external USB drive can cause erratic behavior due to latency. For example, it could cause file corruption or prevent you from saving changes.
- Is this the only file you are seeing this error with?
Thanks for reaching out!
- JaneMullooly-e5Community Member
Hi
I had this problem and it turned out that there was a font in there that the system didn't like.
Best,
Jane
Jane Mullooly | Senior Manager - GBM&T Compliance Training
- EricLoopCommunity Member
Jane and John,
Thanks for your support!
Jane, yes the font seemed to be the trouble.
John, I do, in fact, save to an external drive, but it's not been trouble before. At any rate, I do recognize that since Articulate isn't running natively on my machine and the work is saved externally, I'll have to deal with some minor hiccups occasionally. But this time, it seems a font was at fault.
Thanks again
Related Content
- 3 months ago
- 10 years ago
- 2 months ago