Another migration fix is on the way: https://build.squidex.io/Squidex/squidex/4968
Sorry, but your DB is really fucked up
Another migration fix is on the way: https://build.squidex.io/Squidex/squidex/4968
Sorry, but your DB is really fucked up
Hehe yeah its running with rancher/kubernetes do thats why its a bit harder to use a tool
I am a bit baffled tho how that could be the case. Just tried the whole flow again. With version22 the app starts fine (but no data), with version 21 it resets the version field to 0…
I’ll try again with your next release, see if that helps.
I am thinking I can try running squidex locally to see if that works? Maybe its something in the assets folder, is that even possible?
Been a long time happy user of course hence db fucked up
No, it is definitely not something in the asset folder…
You can try to port-forward your port to localhost, e.g. with kubectl port-forward mongo-0 27018:27017
then you access localhost:27018 to reach your remote mongodb instance. if you have a replica set you have to do it with the the primary node.
I think there is a bug in the migrator, that it resets the version when an exception happens, but this does not explain why an exception happens.
I have fixed the issue with the migrator: Can you reset version to 21 again and then test it out?
Should be ready soon:
That fixes the data issue, I can see my data again! However, new issue Will post in a seperate thread for posterity
Thank you. I have imported it and run the migrator over it and it works fine with dev-4969
.
Unfortunately you cannot go back to a stable 4.X anymore, because the data has been migrated already.
I have another fix: https://build.squidex.io/Squidex/squidex/4970
Same story again: Just rerun the migration. Thank you for beta testing ;)…It is very late here, so you will here from me in 12 hours or so.
How is it going with the fix?
Not sure if this was aimed at me with the problem of 404 when saving, but I went though the restore, version change and upgrade and it worked for me. Still 404 issue tho.
I am thinking i will just setup a new squidex and manually copy/paste data unless @Sebastian you want to debug the issue?
It worked for me, I can test it another time, but I have tested the last try with Marchus_Lamberts change which was also problematic.