This theme has AI generated sections and upgrading the theme will remove those sections as it considered as custom code.
It would be cool to ask the merchant what sections/snippets/blocks he would like to keep during the theme upgrade. This will solve so many issues for many merchants with their theme upgrades.
Yes. It looks like there were several custom sections and they had to be migrated manually. Is there a way to make the process easier during future upgrades?
To make the process easier, I reached out to our theme team for some best practices that can help streamline this process for future upgrades.
For managing these migrations more effectively, I’d recommend taking an inventory of all custom features before starting any upgrade, then checking if the new theme version offers native support for any of those customizations. If the updated theme includes built-in functionality that matches what you’ve custom-coded, you can often replace the custom code with the theme’s native features.
Moving forward, using theme blocks, Custom Liquid blocks, or the theme’s Custom CSS functionality instead of direct file edits will make your themes much more update-friendly since these elements are preserved during upgrades.
Sometimes, we have to upgrade the themes, but the changes were made by someone else. Recently I upgraded a theme from Dawn v6 to the latest version and it was really painful.
It would be nice if there is some UI that asks:
Do you want to keep this snippet? Yes / No
Do you want to keep this section? Yes / No
If there is a custom section that has several app blocks, the section and the app blocks must be re-created and the JSON data must be manually migrate to the new version because the upgrade can’t find the section type.