Word Export in Legacy Mode Not Working Despite Trying All Recommended Workarounds
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Hi Community, We're facing an issue with Word document export in Legacy Mode and have been unable to resolve it despite trying all the workarounds and recommendations shared in existing forum posts and knowledge base articles. Issue Details Product: Articulate Storyline (Legacy Word Export) Export Type: Microsoft Word Document Mode: Legacy Expected Behavior: Word document should generate successfully with all slides and associated content. Actual Behavior: The export either fails, hangs, produces a blank/incomplete document, or does not generate the Word file correctly. Troubleshooting Already Attempted We have tried the commonly recommended fixes, including: Repairing the Storyline installation Updating Storyline to the latest available version Running Storyline with administrator privileges Testing with a newly created project Importing slides into a new Storyline file Shortening file paths and filenames Moving project files to local drives instead of network locations Ensuring Microsoft Word is properly installed and functioning Disabling add-ins and antivirus software for testing Testing on multiple machines and user profiles Rebooting the system and reinstalling Storyline Unfortunately, none of these steps have resolved the issue. Has anyone recently encountered a similar issue where Legacy Word Export continued to fail even after all documented workarounds were attempted? Were there any additional troubleshooting steps, registry changes, Office configuration fixes, or known compatibility issues that helped resolve it? Any guidance would be greatly appreciated. Thank you!Articulate Localization – A Licensing Trap?
Our Situation During the previous billing term, we purchased Articulate Localization credits and used them to translate several courses. However, while our subscription was still active, the licensing terms were fundamentally changed. When our current billing term began, we decided not to purchase additional Localization credits because of these new conditions. At that point, we discovered that the translated courses we had already paid for could no longer be used as expected. What We Find Problematic We paid for the translation of our courses. Nevertheless, without an active Localization license, we can no longer use the translated content in the way we originally anticipated. Most importantly, it is no longer possible to save projects to individual languages or export a translated courses in a single lanuage as SCORM packages. From our perspective, this raises several concerns: Changes to the Licensing Terms The licensing terms were changed during our contract period. As a result, we now have no real options for working with translations that we already paid for than we had at the time of purchase. Previously Paid Translations Are Effectively Locked The translation service was delivered and paid for. However, the translated content can no longer be freely exported and used. From our perspective, it feels as though we are being required to pay again just to access and use content that we already own. Furthermore, the full translation cost is incurred again for every change after the current billing term - even if only a few words need to be updated or a single-language course simply needs to be re-exported. Lack of Transparency Before Purchase Our official Articulate reseller did not inform us that projects created using the Localization feature would become significantly restricted once Localization credits were no longer available. Had we known this in advance, we would most likely not have purchased the Localization feature. No Opportunity to Adjust Our Subscription We made several attempts to change our existing billing term to an annual subscription. Unfortunately, this option was not made available to us. As a result, we were placed under significant time pressure and were unable to properly assess the impact of the licensing changes before making renewal decisions. Our Conclusion We paid not only for the translation of our courses but also with the expectation that the translated content would remain available for long-term use. Discovering that courses that had already been translated could not even be exported as single-language courses once the localization license had expired was neither transparent nor foreseeable. Clear and transparent information about these restrictions would have significantly influenced our purchasing decision and could have prevented a great deal of frustrationMultiple languages in one SCORM
Hi, I can see that there is now an option to publish multiple languages in one SCORM package. This is amazing! However, there is one issue: once you select a language, you cannot change it. Is there a way to refresh or restart the training so that the user can select a different language? Many thanks in advance! :)Localization: Using different embed links and files based on language
Hello, Our teams embed videos via our own platform. Is it currently possible to modify these embed links for each language (so that there is a specific video for each language) without affecting the other languages? The same applies to documents. Currently, the titles of the resources are translated, but we would like to have a different document for each language. Thank you in advance for your feedback. Have a great day, Etienne.Update to the content of training courses that had already been translated
Hello, Currently, I have teams using the translation system, but they’re encountering an issue with training materials that had already been translated. Let me explain: We have existing training materials that were published in X languages (before the translation system was implemented). When we try to translate updates to these modules, the entire module ends up being translated all over again. The problem is that the previous translations had already been approved by the business teams, and they are now being overwritten. Are you considering a way to translate specific parts of the content so we can combine them with existing, already-approved translations? Or is there a workaround that we haven’t identified yet? Thank you in advance for your feedback. Etienne.I Was Wholly Unprepared for NOVA’s Translation and Localization Power!
Yup, We Need This Course Updated by Next Week During the week of Articuland Orlando, my business partners dropped an “immediate need” eLearning build in my lap. At first, I didn’t think it would be a huge lift. Then I realized I had to fine-tune the English version of an existing course and create a Spanish version. Typically, translating a course from English into Latin American Spanish can take us two to four weeks. After I use Copilot to translate the course's script, an internal expert validates the translation. I then make the necessary changes, and the expert confirms that the revisions are correct. The challenge is that my internal expert has a full-time role with the company, so reviewing eLearning translations naturally falls lower on their priority list. When Articulate announced during the keynote that NOVA’s translation and localization feature had been activated for Articulate360 subscribers, I was literally in the middle of translating my course (MANUALLY). What Can It Hurt - Take NOVA for a Spin I said, “What the heck. Even if Storyline is able to only translate the base layer’s onscreen text, that’s a win.” Mind blown, when NOVA translated nearly everything!🤯🤯🤯 It translated: Onscreen text (base layer) Onscreen text (layers) Onscreen text (Master slides*) Changed the language the player was set up in AI Voiceover audio Lessons learned Written Spanish, typically, runs longer than written English. Resizing your text boxes etc. takes time, even with the tool that spotlights exactly where the issues are. *Some Master Slide (layouts) were translated, some were not. I was not working on a highly complex course, so fixing the lingering untranslated Master Slide (layouts) was not a big deal. As mentioned in Articulates Help documentation, when you have hardcoded text onto an image, that will not be translated. I can’t share a full demo, but I captured a few screenshots for your perusal (see below). My Key Takeaway Bottom line, the time NOVA saved us is remarkable. I was so excited, I nearly called my manager to rave about it (even though she was on vacation 🤣🤣).Automatic Selection of preferred language in LMS/SCORM-Package
Hi there, I have a question about the localisation feature in Articulate Rise and would be grateful if anyone with similar experience could help me. 😄 My use case is as follows: Our course content is inside an Articulate Rise course and is exported as a SCORM 1.2 package to a Moodle platform. When the SCORM package is clicked, the user is directed to a pop-up containing the course contents. I understand that Articulate Localisation is the best way to generate and export Rise courses in multiple languages, as demonstrated in the following article and e-learning course: Articulate Localization: Publish Multi-Language Rise 360 Courses | Articulate - Community https://rise.articulate.com/share/wbbxvTJyDgfSsfVryNBVDjvmjdX8agsK#/ The best method I have found is to allow the user to select their preferred language at the beginning of the SCORM package using a dropdown menu, as demonstrated in this article: Multi-SCO SCORM Package with Language Select | Articulate - Community Is there any way to skip the dropdown menu and automatically display the correct course language based on the user's browser language or, alternatively, based on the user's Moodle profile fields? Ideally, this would not require much coding or a custom solution and would not change the current user flow when accessing course content. Any help or feedback on this issue would be much appreciated. 🙏 Best regards, FelixSwitch languages from within Rise 360 course using Articulate Localization
Hi! We have used Articulate localization to translate our course into 5 languages. We then export to one SCORM package that contains all of the languages. We use that SCORM file in 2 LMS's. In Litmos, the user is presented with the language, they choose the content and off they go. If they decide they want to go back and choose English instead (it's technical content, this is common), they simply exit and go back in and they'll have the option to choose the language again. It keeps track of where they were, just presents in the new chosen language. All works great. In Thinkific, once again the user is presented with the language choice when first entering the course. However, whatever language they choose "sticks." There is no way to switch to a different language if they accidentally chose the wrong one or want to go back to English. When they exit and come back in, they come back in in the same language with no option to choose another one. Is there a way to present the option to switch languages from within the course? I'm using Rise 360, not Storyline. I found this previous article, but I think it's meant for Storyline? Articulate Localization | Articulate - CommunityError publishing upload a SCORM package I've translated using localisation
Hi I've translated a storyline course and published to LMS just one of the languages. I translated it from English to French and only want the French version in my Brightspace course container. I published fine and can view the file fine. Then I zipped it up and tried to upload to Brightspace but it fails with the error message "The package is missing a manifest". I've never had this error before and this is the first time using localisation. Has anyone else experienced this?How are you designing courses for localization from the beginning?
I've been thinking a lot about localization as a design decision rather than something that happens after a course is built. One thing I've learned from working on global learning projects is that decisions made early, including how text is handled in graphics, how media is structured, how reviews are managed, and how the course is packaged, can make a huge difference once you begin scaling across languages. I'm curious how others approach this. What are you doing during the design and development stage to make localization easier later?
