Articulate Studio 13 problem when publishing

Oct 19, 2017

We recently had a problem when publishing a file in Articulate Studio 13. We had 3 languages we were working on (ES, TR and ZH) and when publishing the TR, half of the course was in TR and half in ES. That was imposible because the file was completely in TR. A PPT file was the source. We used PPT 2007. We cannot replicate the issue but we are wondering how this could have happened. Attached the published file. The problem can be seen in the first slide.

10 Replies
Alyssa Gomez

Hi Selene,

How strange! I can't say I've come across an issue like this one before, so I'm really glad you reached out. 

Aside from the published output file, could you also share the unpublished Articulate Package with me? Here's how to make an Articulate Package. 

Also, on what slide does the language change from TR to ES? Could you share a screenshot of those slides, as well? Thanks!

Selene Redigonda

The files were sent via we Transfer to the e-mail
reply-470932@heroes-prod-reply.articulate.com! We used some of the
translation features to modify the project, for example we used the
default labels, and manually Localized the menu titles. We also imported
the localized text to the quiz files. This problem we are referring to
was completely random, we cannot replicate it again, but concerned us.

Selene Redigonda

I have sent the files via wetransfer to the e-mail
reply-470940@heroes-prod-reply.articulate.com. Regarding the slides, the
first slide already has the problem. I sent the published version of the
course. In any case, see the screenshots below, the file was completely
in Tr and for some reason ES text appeared...

Ashley Terwilliger-Pollard

Hi Selene,

Thanks for sharing the images and a copy of your project. I took a look and while editing and in my published version the languages looked the same. Take a look at the example I posted here to Tempshare.  (it'll be live for 10 days) and I've also attached the published output folder for you. 

Were you seeing this while editing or while looking at the published output? Perhaps you were using slides or items from the other version of the course? Or the browser was caching an older copy with the other language display? It doesn't appear to have carried over to the files you shared or as a part of my published output. 

Selene Redigonda

Hi Ashley, we have the problem in the published output. We published the course with the same PPT I sent you (completely translated to TR)  and half of the published version was in TR and half in ES....there were no Es texts in the PPT... the second time we published, it was ok.

What we are wondering is how a file completely localized in TR could display ES text in the publish output...we were also localizing the PPT to ES but was a different file.

Thanks for your help.

Just in case, I am re-attaching the published course with half of the text in TR and half ES...this happened only once, but we delivered this to the client and have a feedback back asking how this could happened.

Ashley Terwilliger-Pollard

Hi Selene,

You didn't see the issue in my published version though, correct?

I can't say how it may have happened, but I could speculate that some elements of both the TR and ES file were somehow connected and perhaps shared some slides to start with. Did this only happen with the one course? Could you have used the same Translation export/import .doc files for both?  After you published the course, did you see the language differences in the published version? Did you view that locally or up on a web server/LMS?

I'd confirm that you were following along with the guidelines here to prevent odd behavior in project files (that could ultimately lead to corruption).  

Let us know if you consistently run into the same issue and we can dig a bit deeper!

Selene Redigonda

No, not in the published version you sent or the one after the problem. It was a one time problem. We used different files and different folders for ES and TR, they were not under the same path. We see the problem in the published version if we view it locally or LMS, or in a server. It always appears. Regarding the guidelines, we use a server to work to avoid having local projects since the server has a constant backup of the files. I do not think that that could be the problem. If this is just a random problem I will share this information to the client.

Ali Goulet

Hey Selene!

Thanks for those additional details. I'm leaning toward this being a random issue, however we do always recommend working locally as working from a network can definitely cause erratic behavior in your files.

If you run into this issue again, don't hesitate to give us a shout here! Good luck with the rest of your project ☺️

This discussion is closed. You can start a new discussion or contact Articulate Support.