Improve Autosave App

We have installed the ‘autosave’ extension app across our Storyblok spaces and it has introduced several hurdles in the content workflow that we would like to resolve:

  • Scenario 1: Editor adds new block and immediately sees error message “Saving failed. Please check if you’ve filled out all fields correctly.” before editor has a chance to fill out required fields

  • Scenario 2: Navigating out of a nested block too quickly after making a change will cause autosave to miss the change and changes will be lost

  • Scenario 3: On initial page load, Editor starts typing immediately and then autosave kicks in a few seconds later and reverts back to the latest saved version so you lose the first few words you type. This issue only occurs on initial page load

  • Scenario 4: Autosave creates versions for each small change that is made, making it difficult to revert back to the right previous version with so many records to sort through

  • Scenario 5: Editor will manually click save when autosave is enabled and see error message “Content Conflict. A newer version of this content item has been found in the database. Please choose how you want to proceed.” Please note: This issue has occurred only when autosave is enabled and when we only have one url open in the tab and/or there has been only one editor editing the page at a time

1 Like

Hello @taylorperras,

do these points apply to the V1 or the V2 UI implementation of the autosave app?

Thanks in advance!

Best regards
Hannes

Hi @Hannes, the experience with the autosave app installed is similar across both the v1 and v2 implementation of Storyblok. We do feel like scenario #1 is less disruptive (less jumping around on page when error message is displayed) in the v2 iteration of Storyblok, but then scenario #3 seems to be more prevalent in v2.

Thanks for looking into this!

Hello @taylorperras,

thanks a lot for the feedback! I will forward it to my colleagues and keep you updated.

Best regards
Hannes