Forum Discussion

Jürgen_Schoene_'s avatar
Jürgen_Schoene_
Community Member
2 years ago

new storyline version (3.76) - new bug

after 5 minutes testing: with the new version the logic of the name of the publish folder is changed again - no infos in the release notes !!! ... V3.69 - Titel "empty-3.69" -> publish folder "e...
storyline 360
  • LucianaPiazza's avatar
    LucianaPiazza
    2 years ago

    Hello Everyone! ✨

    I'm happy to share that we have released a new update for Storyline 360 (Build 3.77.30568.0).

    In this update, we have implemented a fix for:

    • Storyline 360 could crash when projects had special characters in their titles. Output folder names may be different from project titles.

    As a first step, I recommend updating Storyline 360 to the latest version. Here's how:

    Update Authoring Apps

    If you have any questions, please let us know in this thread or privately in a support case.

    Have a great day! 

Jürgen_Schoene_'s avatar
Jürgen_Schoene_
Community Member
2 years ago

Title: ")))))" -> Storyline 3.76 crashes without any error message (while starting publish to web)

@articulate: please test your software before publishing new versions !!!!!

  • EricSantos's avatar
    EricSantos
    Staff
    2 years ago

    Hi Jürgen,

    Good catch! We're already looking into these bugs introduced in the latest Storyline update: 

    • Putting a dot on the title will result in an extra space in the output folder during publishing.
    • When publishing, Storyline removes the closing parentheses from the folder title. Numeric characters and dashes are also removed from the beginning. A related issue is that using only closing parentheses causes a crash without an error message.

    We'll update this post once these problems have been addressed. In the meantime, we recommend renaming the output folder names; the title of the course itself and the zipped output are not affected.

    Regarding the Storyline Version History, our public release notes are prioritized based on impact, and we include high-profile bug fixes that affect many customers. Bugs with very limited impact, determined based on support cases, ELH discussions, and Storyline error reports, may not be listed. However, we contact every customer who reported an issue to let them know it's fixed, even if it doesn't appear in the public release notes.

    Let me know if you have additional questions. Thank you, Jürgen!

Related Content