Forum Discussion

cyndyryder's avatar
cyndyryder
Community Member
7 years ago

Text entry field - new error since last update

Hello,

We have many courses that require learners to input their names before beginning the module. There is a text entry field with the following code:

"Set LearnerName equal to the typed value When the control loses focus".

Then we have a "Confirm" button, with the following code:

"Change state of Error (a warning message) to Normal When the user clicks (Confirm) IF LearnerName is equal to (blank).

Change state of Next Button to Normal When the learner clicks (Confirm) if LearnerName is not equal to (blank)"

This has been working well for years. However, since I updated Storyline 3 to the latest release, the variable LearnerName does not register if I click Confirm (when published). I have to click somewhere else on the screen before clicking on Confirm (even if pressed multiple times).

I have attached a sample.

 

***EDIT: I can also confirm that courses published before updating Storyline 3 still work properly. Only courses published after updating present this error.

19 Replies

  • Hi I have just started experiencing this issue, it previews fine but when published and playing in IE11 it doesn't pull through the person's name - Text Entry 2. I updated my version of SL3 relatively recently and it worked fine before.  Could someone take a look for me please?

    • BeccaLevan's avatar
      BeccaLevan
      Community Member

      Thanks for reaching out and sharing your file, Amanda! 

      I tested this out in IE11, and I see the same behavior you described where the text entry value doesn't carry over. Things worked as expected in Chrome and Firefox for me.

      From here, I've enlisted one of our support engineers to help troubleshoot and opened a support case on your behalf. One of my teammates will reach out shortly!

      • Amanda-Gunning's avatar
        Amanda-Gunning
        Community Member

        Thank you so much for helping with this. The engineer has provided a workaround of adding another button over my existing button.  So the user has to enter their name, press enter (which changes the hidden start button to normal), then press start. Hope the bug gets fixed soon.

  • I appreciate the update, Amanda. I've linked this conversation to our report as well so that we can share updates with you here.

  • Hi, everyone.

    I just wanted to share that we no longer see the bug reported where setting the variable when pressing the button is not working as it was previously using the latest build of Storyline (3.61.27106.0).

    If you're using the latest version and you're still experiencing this issue, please reach out to our support team through a case