Forum Discussion
Copy of a localized (multi language) file cannot be published to a NEW review name
HELP!
I created a file and localized it with English/Spanish. I published for review. It went great. Now I need to make a similar file, so I started with my existing file and made a copy of it. Made a whole bunch of changes, updated translations, etc. But when I go to publish to review 360, it wants to publish to the original review. But this is a NEW file. How do I fix this? Do I have to start over every time with a non-localized file and redo all the formatting (getting rid of scroll bars, etc) again? I should always be able to publish as a NEW review when I want to. Please advise.
5 Replies
Can you clarify? Save translation as only saves one language. I have a file created in English and translated to 4 different languages. Are you saying I can save an English version, a French version, a Spanish version and a German version but I cannot save a version that has all 4 languages in it? Because that's what I want to do. The translations have already been vetted and verified by my staff. I don't want to start over with translating from English again.
Thx
Hello lorraineS,
I see that you've opened a case and that you are working with my colleague John Carlo. You're in excellent hands! They'll be in touch shortly via email to follow up.
Have a wonderful start to 2026!
Was there any fix for this? I'm currently having the same issue.
ThanksHi StephClark,
Sorry to hear you're also having trouble publishing copies of localized courses to Review 360.
Great to see that lorraineS has been helping you. I see that she's also been working with my teammate Mcgem, through a support case. As he shared:
"Localized (often multi-language) projects can have only one corresponding item (stack) in Review 360. When you republish a multi-language course to Review 360, Storyline doesn't create a new stack. Instead, it adds new versions of the languages within the existing stack.
Storyline 360 preserves the link between your project file and the Review 360 stack even if you create copies of the file (for example, using Save As or sharing the file with other authors). That's why publishing from those copies still updates the same Review item, and you don't see the normal option to publish a new item.
If you need a brand new Review 360 item, use Save Translation As to create an independent copy of the project/language and publish from that new file. To save an individual language as its own project file, hover over the language you want and select Save Translation As. This can also help if:
- You want to create an entirely different course layout for a subset of your languages (e.g., RTL languages).
- You want to open your project in the retail version of Storyline.
- You need to share a localized file with a Storyline user who does not have Articulate Localization enabled.
- You need to back up your project and want a separate backup project file for each language.
- You want to author and review text in a single file, but each language has its own media.
When you use Save Translation As, the new file is independent and not linked to the original multi-language project. Publishing it will create a new Review 360 item".
However, I understand that you and lorraineS would prefer an option to allow multi-language courses to have more than one corresponding stack in Review 360. I've shared your requests directly with our product team.
We'll be sure to notify you if we release a future enhancement that helps!
