- edited description
Migration has failed. Check console errors for details.
I am currently using Foundry Version 11 Build 302, Obisidian 6.5.6 and Dnd5e 2.2.1. I believe this issue is a bug as I deactivated all my other modules and the error still occurs. I’m trying to use Obsidian on a world that I’ve updated from Foundry Version 10 to 11. When I load the world with Obsidian activated, Obsidian provides this prompt:
After clicking “Begin Migration“, I’m met with this:
When I check the console log there are many errors messages which say this:
The only way I can get out of the error message in the second image is by reloading the world and clicking “Cancel Migration“.
I am still able to change the character sheet to Obsidian for my players, but when I do so I cannot access their character sheets.
If I try opening a character sheet after changing it to Obsidian, the console shows this:
I’m not a programmer of any kind so I won’t be able to provide more information unless I know what to look for. If there’s any way to fix this please let me know!
Comments (8)
-
reporter -
reporter - edited description
-
reporter - edited description
-
repo owner Those error messages from the migration are harmless. I’d need to see what the last error message is to understand why the migration failed. Either way, if you could zip up your world data (I just need the data, nothing else), and send it to me, I can take a look. I can see other modules in your error messages though, so please make sure to disable them all, then retry the migration first. If it’s still a problem, send me the world data.
-
reporter Thank you for the quick response! Here is my world data. I tried it again with all my other modules disabled and it still didn’t work. This was the final error message in the console:
-
reporter Just an update - it appears a new update for Obsidian has come out and it now works. Thank you so much! You’ve done an amazing job with this sheet it looks amazing.
-
repo owner - changed status to open
-
repo owner - changed status to resolved
Nice, glad that fixed it for you
- Log in to comment