Can I upgrade my Squidex from 4.2.0 to the latest version from GitHub (6.0.1) or is it better to use an intermediate version?
I think a big version jump can be painful to implement
I would make a backup or clone your collections and then try it. If it does not work for whatever reason you can send me the old backup and I will have a look asap.
Okay, please send me your mongo backup.
I’m preparing the backup. I’ll send to you asap.
Sorry about the previous broken link to bkp. I have sent another link that should work.
I have found an error with your data. Some of your content items had 2 consecutive “ContentDeleted” events and the migration process was not able to handle this.
I have a fix ready. Will provide you the docker tag when it is ready.
I’ve checked out to the master branch and set the flag to false, but I’m still experiencing the same problem described earlier https://github.com/Squidex/squidex/commit/d338fbb14a7ed006382f2ae1acb2758b2eb91944
I can try it again with your backup, but It was working for me.
I cannot reproduce it. If you are using the debugger you have to step over the NullReferenceException.
It works after a few “step over the NullReferenceException”, more specifically three times.
Thanks a lot @Sebastian
After upgrade these content items are not available. You have to to get the IDs of these items
And then you can delete the last ContentDeletedEvent.
Just filter for
in the Events2 collection.
After that you have to rerun the content rebuild:
Set this property / config to true: https://github.com/Squidex/squidex/blob/master/backend/src/Squidex/appsettings.json#L519