Stackable ver.3 Migration Settings should default to Load version 2 blocks in th

  • Resolved Giorgio25b

    (@giorgio25b)


    3 years, 1 month ago

    This major upgrade is pretty disruptive and the change from ugb to stk should have been flagged with the update notice, such as:

    This upgrade will break all your custom work unless you properly set yourself the Migration Settings

    Changing the blocks prefix should have been done in the first place ages ago, but regardless, the default settings for the migration are not working when set to Load version 2 blocks in the editor only when the page was using version 2 blocks thought they work when set to Load version 2 blocks in the editor

    It’s your call but this was not handled properly and the communication with major breaking changes should be clear and easy to implement.
    So for other people reference this is what I changed in order to have the “older” blocks still rendered as blocks and not as html:

    stackable-ver-3-migration-settings

    Hope this helps,
    Giorgio

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Benjamin Intal

    (@bfintal)

    Thanks for the heads up. It appears that sometimes the onboarding and migration wizard is not being shown. During onboarding, you should have been asked about that option.

    We’ll be addressing this!

    Plugin Author Benjamin Intal

    (@bfintal)

    Version 3.0.1 should have fixed the issue!

    Thread Starter Giorgio25b

    (@giorgio25b)

    @bfintal Version 3.0.5 addresses the previous versions issues in a way that is just outstanding.

    Excellent work #Stackable and thanks for pushing a much better UI/UX.

    Tested on 3 different sites and it went really smooth on all of them.

    Plugin Author Benjamin Intal

    (@bfintal)

    Happy it went great @giorgio25b !

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Stackable ver.3 Migration Settings should default to Load version 2 blocks in th’ is closed to new replies.

Tags