Back
Errors during migration
Are these errors ok to ignore? If not, is there a SQL command I can run to fix what's needed? This has been my instance since 0.6 and it's live in production. I can't afford for it to screw up.
1.4.4 > 1.4.14 https://pastebin.com/hxNz4Ypw
1.4.14 > 1.5.3 https://pastebin.com/wMh4J7Fq
TL;DR
Developers experiencing migration errors while updating from 1.4.4 to 1.4.14 and then to 1.5.3. They seek to know if these errors are safe to ignore and if there's a SQL command to rectify the issues. The system has been live since version 0.6 and any potential downtime can't be afforded.
Solution: A thorough manual inspection of the errors in the provided pastebin links is necessary to determine the severity of each issue. Running SQL commands to fix specific problems might be possible, but it's advised to back up all data before attempting any alterations. 