Open halfer53 opened 1 year ago
Hi there @halfer53!
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
Complete log file: https://mega.nz/file/Fd8WmZSB#JColfshGyKR4Y3qOH5QNbUjkiM6pmLbe9yrm2GFsdv8
Hey!
Thanks a lot for posting this issue 💪. I tried reproducing by upgrading a v 8.17.0 project with the clean starter kit installed to 10.5.1. And it worked. Are you able to provide us with your database so we can look further into the issue? 😄
@andr317c sure, how do I send the database to you?
You can send a backpack of your database to my email: aze@umbraco.dk
I looked further into the issue and found out that we have an issue with translating Chinese and some other special characters to a PropertyTypeGroup alias, the issue left some aliases empty which is why this upgrade failed.
I'm guessing that we did not have a validation checking if the PropertyTypeGroup alias was empty or not. in V7 and under.
To fix the missing aliases on your PropertyTypeGroup, go into your cmsPropertyTypeGroup table and add the missing aliases for the PropertyTypeGroups.
The actual issue happens when you try to input Chinese or some other special characters in the PropertyTypeGroup name for the first time and try to save it, the alias for the PropertyTypeGroup will be empty.
An example could be that you try to input "内容" as the PropertyTypeGroup name, when you input this, the alias will be empty. This will throw a validation error on V10 and up so you won't be able to save the document type, my guess would be that on earlier versions around V7 and under it did not throw an error, so you were allowed to save a PropertyTypeGroup with an empty alias. If you then try to write "内容内容" it will set the alias as "1" and it will save the document type. The alias should be translated to "1" the first time we input the PropertyTypeGroup name, and not the second time.
I will mark this issue as an up for grabs.
Hi @halfer53,
We're writing to let you know that we would love some help with this issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.
For more information about issues and states, have a look at this blog post.
Thanks muchly, from your friendly Umbraco GitHub bot :-)
possible workaround find all Property Type Group with empty alias and set it SELECT * FROM [cmsPropertyTypeGroup] WHERE [alias] is null
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
10.0.0
Bug summary
I'm trying to upgrade the database from 8.17.0 to 10.0.0, then I got the following error. The same error can be reproduced using 10.5.1
Specifics
Context: I'm upgrading an old umbraco project from 7. I removed and updated some of the data properties and managed to successfully upgrade to 8.17.0. But I am unable to continue down the path of upgrade to 10 due the above error.
Steps to reproduce
Have my 8.17.0 database Install a new Umbraco 10 project Hit upgrade, failed with the above exception
Expected result / actual result
Upgrade should be successful