Problem with states names and langage

Hi Storyliners,

Sorry for my english... I'am working with SL2 (update 5), in the French interface. When I create an state "Survol" (= state "over" in french), the interaction don't work, like if SL don't recognize "Survol" as "over". Any idea ? Is another problems working in a specific langage interface ?


26 Replies
Ashley Terwilliger-Pollard

Hi Raul,

I'm just following up as I see that Abel was testing your course and reproduced the issue. He shared this with our QA team, and indicated that it is happening when you use the Duplicate option when editing states. When "Survol" was selected, Storyline treated it as a custom state instead of a built-in state. As a workaround please look at using the New option instead of Duplicate. 

Ashley Terwilliger-Pollard

Hi Jan,

The issue detailed here is still with our QA team for review, and I don't have an update in regards to a fix or additional information. The current workaround is to select "New" instead of "Duplicate" when editing states or use English language when working in Storyline User Interface.

Ashley Terwilliger-Pollard

Hi Jan,

It is not fixed as a part of Update 7. You can always see what fixes or updates were included as a part of the release notes detailed here: 

New Features:

  • Added support for Apple iOS 9
  • Added support for Google Chrome 44 and later on Android devices

Bug Fixes:

  • Fixed issue where a lengthy course could lock up during preview or playback in a Flash-enabled browser
  • Fixed issue where right-click triggers wouldn't work on base layers in Flash output
  • Fixed issue where key-press triggers assigned to the slide wouldn't work after clicking the slide in Flash output
  • Fixed issue where pressing arrow keys would highlight items in the menu rather than moving objects on the slide
Jan Vilbrandt

Hi Ahsley,

I know this list and the place where to look.

It would be very helpful if the programming team remembers to fix that bug!

I cannot install update 6+7 because of two bugs Articulate did NOT fix THOUGH the programmers know that the bugs are there.


I wish Articulate would care more about service and their customers.

Ashley Terwilliger-Pollard

Hi Jan,

Thanks for reaching out here again. We're unable to share information in regards to a timeline for product updates or new releases, but as Justin mentioned he brought this issue to the attention of our QA team and we'll keep you posted here once there is any additional information to share. 

It does seem that this issue has a workaround in regards to not selecting "duplicate" when editing states while using a different language UI, you can select "new" instead. 

Jan Vilbrandt

Hi Ashley,

there is a workaround for that Problem, agreed.

BUT what about the other bugs like drag & drop -> tile. What is the solution for this bug?

Not answering my question and hiding behind some company policies does not help :-(

I do not like the way Articulate takes not care about their customers... sorry... but there are unsolved problems. I am still using SL 2 with update 5 because of the bugs Articulate did create within updates 6 and 7 and the need for a functioning drag & drop tiling... but I will need the iOS 9 compatibility for my next project!

Ashley Terwilliger-Pollard

Hi Jan,

I'm truly sorry that I don't have additional information to share about the issue you mentioned with the tiling of drag and drop items and that you feel you're not being taken care of. That is certainly not the experience we want you to have as a customer and contributor in our forums. As Justin mentioned to you in another thread the tiling issue is something he brought up directly to our QA lead, and that once we have additional information to share in regards to a fix or a workaround we'll share in the thread where it was originally discussed. 

If there is additional issues you'd like to discuss I'd invite you to connect with our Support engineers here and please let me know if you choose to take that path and I can ensure you're case is assigned to one of our senior engineers. 

Christie Pollick

Thank you so much for noting the additional behavior you have encountered, Aurelien!

The matter is still in the hands of our QA team, and although I do not have any additional updates to provide at the moment, we will be certain to share anything more as it's received here in the thread. Your patience is appreciated! :)

Ashley Terwilliger-Pollard

Hi all,

I wanted to provide an update here, as Storyline 2 Update 11 was just released, and included a number of fixes which you can see in the release notes available here. The item you all may be particularly interested in is how it fixed an issue where:

  • Fixed issue where the default behavior for built-in states wouldn't always work when the Storyline interface was localized in Chinese, French, German, or Spanish

You can download the latest update here, and after downloading and installing the latest update you’ll want to republish any existing content to ensure that the updates and fixes are applied.

Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Miriam Calvo

Hi there!

I´m using the sl2 update 11 (1609.3020) but we still having problems with states in spanish. Lately we have issues in using drag and drop states. Everything works fine in english, but when someone of the team uses SL2 in spanish the states doesn´t work (I think there are built-in states as drop correct or drop incorrect). Is there another version different than mine?