Forum Discussion
New in Storyline 360: Text Autofit Enhancements
We know how important it is for all learners to easily access and read the text in your courses, which is why we’re excited about the improvements we’ve made to the text-authoring experience in Stor...
After sleeping on the problem, both solutions I tried are not acceptable. If we are unable to open SL pre V52, in V52 that is a major error/bug. If I need to update content, it would mean hours of tedious labour to copy content; slide title, slide text or other content, notes, and text to speech. I guess SL Engineers better get busy.
I agree that this is certainly a major bug. I've just tried creating a new file in v3.52 & saving it without even adding any text fields! And it won't open in an earlier version of SL360 giving the error message:
This project won't open because it uses features that aren't available in this version of Storyline. The features in use are:
Text Scrollbars
Install the latest Storyline update to open this project
There's absolutely nothing in the file at all apart from a single blank slide so this message is obvious nonsense.
Like many SL developers I frequently have to rollback SL versions or resort to using an older version of SL360 I keep installed on another PC for emergencies, in order to work around some of the worst bugs that now invariably appear with new updates, so I can see this latest issue becoming a major concern.
It is one thing for updated file formats not to be forwardly compatible between major releases but for this to happen between minor updates, and without any advance warning being given by Articulate that I have seen is wholly unacceptable. Note that no warning is given in either in the article above or when you click the 'Upgrade Project Text...' button in Format Shape | Text Box. Even more irksomely, in the Storyline 360: Text Autofit Improvements article linked above there is actually a Compatibility section ... which makes no mention that they've broken it!
Surely it cannot be beyond the wit of the SL developers to support new features in the updated file-format without breaking it for all older versions?
This is reminiscent of a similarly vexing issue with Text Styles that can break file compatibility between minor versions seemingly randomly i.e. a SL document apparently being tagged as using Text Styles, even though none have been consciously used. This then prevents it being opened in an older SL360 installation.
