Upgrading from Umbraco 13 to Umbraco 17 may result in Block List/Grid items appearing as Draft and non-default languages showing empty content due to configuration mismatches. Johan Reitsma outlines the issue's this causes, provides an SQL fix to apply before upgrading, and details validation steps to ensure proper functionality post-migration.
Johan Reitsma talks about how upgrading from Umbraco 13 to Umbraco 17 involves a structured, phased approach focusing on analysis, validation, and incremental upgrades. Key phases include database validation, core project upgrades, custom property editor adjustments, and thorough testing, prioritizing backoffice stability. This method ensures a manageable and predictable upgrade process across projects.