[Solved] Upgrading to Umbraco 13 breaks changes pa...
# help-with-umbraco
t
Example, we have a node with slug/path/url
/sok
, this is for "sök" which is Swedish for "search". So the
name
of this node is "Sök". Switching over to Umbraco 13, from Umbraco v10.8.5, we are greeted with the "complete the installation" part of the upgrade where database migrations are run. However, after this upgrade any
åäö
characters in node names are interpreted the wrong way and the paths are rewritten. We found the reason! We have our RequestHandler.CharCollection defined in version 10, but this has been renamed to UserDefinedCharCollection In our above example,
/sok
become
/soek
, but changing to
UserDefinedCharCollection
fixed this so it's back to correct url. However.. NESTED content displays issues. For example we have a node called "Äldre" which pre-migration has path
/vart-sociala-arbete/for-manniskor-i-utsatthet/aldre/
but post-migration it is changed to
/vart-sociala-arbete/for-manniskor-i-utsatthet/aeldre/
, as if it does not respect the
UserDefinedCharCollection
. Is there any way to prevent this? Or to easily change this afterhand? If possible we do not wish to add the
umbracoUrlName
on affected nodes if not absolutely necessary.
Found the solution for future reference: If you set
"EnableDefaultCharReplacements": false,
then there wont be any conversion happening at all during the migration. Afterwards you can remove this property again.
26 Views