I've had a dive into the Umbraco source and ripped out some code in order to write a console app to trigger an Umbraco upgrade using some of the Migration Runner code. I've consulted the tests for this (in Umbraco.Tests) and believe I have something that works, however after I've run the app, all nodes are flagged with the red asterisk to indicate that the page has been saved. There is nothing in the logs that indicates an error occurred and the database appears to have upgraded successfully. I'm trialing this on a 4.7.2 site, and upgrading through to 6.1.6.
Anyone know why my nodes are appearing as though there are pending changes?
using Migration Runner for Umbraco upgrades
Hello,
I've had a dive into the Umbraco source and ripped out some code in order to write a console app to trigger an Umbraco upgrade using some of the Migration Runner code. I've consulted the tests for this (in Umbraco.Tests) and believe I have something that works, however after I've run the app, all nodes are flagged with the red asterisk to indicate that the page has been saved. There is nothing in the logs that indicates an error occurred and the database appears to have upgraded successfully. I'm trialing this on a 4.7.2 site, and upgrading through to 6.1.6.
Anyone know why my nodes are appearing as though there are pending changes?
Thanks!
Braydie
is working on a reply...