We plan to upgrade a few quite big v7 websites to v10.
So the issue is that we need to track content changes made on the old v7 live site while we are working on the upgrade.
Can we use some existing package, or how can we track all content changes for a while on v7?
You could maybe use these APIs to build a tool that could loop through the version differences for all content nodes between 2 specific dates (i.e. the DB when you started the upgrade, and the DB when the upgrade is ready to go live), and then adapt this to your needs, i.e. getting the most recent content version, detecting differences in certain fields.
I don't know the service off the top of my head but hopefully this might get you in the right direction!
Track content changes during Umbraco Upgrade
Hello Community,
We plan to upgrade a few quite big v7 websites to v10. So the issue is that we need to track content changes made on the old v7 live site while we are working on the upgrade.
Can we use some existing package, or how can we track all content changes for a while on v7?
Thanks, Alex
Could you look into the underlaying API's that power the Umbraco rollback feature, specifically the content differences between node versions?
https://our.umbraco.com/documentation/tutorials/editors-manual/Version-Management/Rollback-to-a-Previous-Versions/
https://our.umbraco.com/Documentation/Tutorials/Editors-Manual/Version-Management/Comparing-Versions/index-v7
You could maybe use these APIs to build a tool that could loop through the version differences for all content nodes between 2 specific dates (i.e. the DB when you started the upgrade, and the DB when the upgrade is ready to go live), and then adapt this to your needs, i.e. getting the most recent content version, detecting differences in certain fields.
I don't know the service off the top of my head but hopefully this might get you in the right direction!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.