Forum Discussion
English state overwritten with changes in other language, quiz questions, storyline 360
We've come across a weird bug.
Storyline 360 (version from 6/9 - we can't upgrade due to the closed caption issues in 6/16 and 6/23)
File is in 10 different languages with English as the source language.
I have question slides. Originally, answer options just had normal, hover and selected states. I added a disabled state to each option and set that as the default. Once audio is over, I set the states to normal. When I edit the disabled state for a non-English language and then flip back to English, the button now reads in that other language in the disabled (default) state! This is causing all kinds of grief and thank goodness we notices before delivering to the client. I should have to go back and recheck English when I'm adding another localized language to the file.
Has anyone else experienced this? Know of a work around? Reported it as a bug?
Any advice is helpful!
Thanks,
Lori
12 Replies
Hi lorraineS,
It sounds like target language edits are affecting source language elements in Storyline.
That shouldn't be happening, and I can understand how disruptive this can feel. Based on your description, I replicated a similar design. However, I could not reproduce the same behavior when testing in the current version of Storyline, or 3.119.
Can you confirm that you're working with locally-stored .story files? Authoring directly from a network drive can introduce latency and issues such as this. If you're already working locally, please try a repair of your Storyline installation.
If that doesn't do the trick, it would be helpful to see the affected .story file. Do you mind uploading a copy here in the discussion or through a support case?
I ALWAYS work with locally stored .story files. I know not doing that can cause all kinds of problems.
I can't repair my storyline because I need to stay on the version from 6/9 and that load is not available anymore. The loads from 6/16 and 6/23 have closed caption issues. CCs disappeared in all languages. A bug report was submitted by my teammate Teo ([email protected])Both Teo and I experienced the same behavior.
Hi lorraineS,
Thanks for confirming those details. I also appreciate you sharing that both you and your teammate are seeing the same behavior while working with locally stored Storyline files.
I can confirm that Teo has already opened a support case and is working with Carlo to investigate the multilingual issues you're experiencing. At this point, we haven't confirmed a related bug, so we'll continue troubleshooting through the support case to better understand what's happening.
We'll keep you updated there as we learn more.
i am facing the same problem, specially the states of the buttons are translating to localized languages. also the markers showing same behaviour. this is happening after the latest updates
Hi SudeepaGanguly,
Sorry to hear that you're also experiencing this behavior with a localized .story file.
I've opened a support case on your behalf and sent you an email with an upload link you can use to share your file privately. You're in great hands working with our support engineers, and we can continue the conversation through your case.
yes i received the mail, but i manually changed the state back to english, hence the project file do not reflect the issue. my team members also faced similar issue and manually changed it back to english, as major deadline was nearing and we cant keep waiting for articulate to come back on the issue.
I hope you have also reported this as a bug to Articulate. We need to get these things fixed!
Hi lorraineS,
Thanks for continuing to raise awareness of this issue.
I noticed you're already working with Christian in your support case, and he recently shared an update after narrowing down some conditions where he could reproduce similar localization behavior. If you haven't seen his latest email yet, it may be worth checking your spam or junk folder just in case.
When you have a chance, could you let him know whether you're able to reproduce the same results with the sample Storyline file he shared? That comparison will help us continue narrowing down the conditions behind this behavior.
We know how disruptive this has been to your localization workflow, and we're committed to working through it with you. We'll continue the investigation in your support case and share any new findings as soon as we have them.
Similar issue for me. We received a call from one of our users about a course we are offering in both English and Spanish, because some of the text was unreadable. As I investigated further, I found some 60+ issues that had occurred in the base English version, including changed fonts, font colors, button states, text box sizing issues, and English closed captions that now included about 10% Spanish. I ended up having to create separate English and Spanish Storyline files so I could fix the issues.
Please report this to articulate as a major bug. We need them to stop breaking things when they add new features! This did not occur before the June versions.
Hi, TheOGMike! Thanks for sharing what you ran into. I understand how frustrating it must have been to find those unexpected changes after your course had already been localized, especially with the amount of manual cleanup you described.
We'd like to take a closer look at what you're seeing. Could you share the affected Storyline file with us privately through a support case? That will help us determine whether you're experiencing the same localization behavior that's already under investigation or something different.
Once we have your file, our support team will work with you to better understand what's happening and keep you updated along the way.
Thanks, Eric. Just submitted my file.
