v7 > v8 upgrade. Lost data in nestedContent + relatedlinks
We're doing a large scale upgrade at the moment and I've been trying to track down where some related links data has been lost. It seems to happen during the v7 > v8 upgrade when the json format for these items changes.
In v7 I have a nestedContent item called 'Tab items'. This contains an element called 'Quick links' which is a related links picker.
In the v7 db, the json for an item inside this looks like (indented to make easier to read)
Our upgrade process to get to v8 involves
Fresh copy of v8.18.8
Install proworks v8 migrations package
Change connection string to v7 db, run and let it upgrade
When this is complete, the links are gone from the backend
db shows this stored value, note 'link not url' and 'caption not name'
I then manually created a new quick links item to compare in the db
db textValue looks like
Until the page is saved, the data for the existing item is still in the db albeit with incorrect formatting but on save it gets wiped out as shown above for the first item within quicklinks.
Has anyone seen this before or have any ideas we could try?
v7 > v8 upgrade. Lost data in nestedContent + relatedlinks
We're doing a large scale upgrade at the moment and I've been trying to track down where some related links data has been lost. It seems to happen during the v7 > v8 upgrade when the json format for these items changes.
In v7 I have a nestedContent item called 'Tab items'. This contains an element called 'Quick links' which is a related links picker.
In the v7 db, the json for an item inside this looks like (indented to make easier to read)
Our upgrade process to get to v8 involves
When this is complete, the links are gone from the backend
db shows this stored value, note 'link not url' and 'caption not name'
I then manually created a new quick links item to compare in the db
db textValue looks like
Until the page is saved, the data for the existing item is still in the db albeit with incorrect formatting but on save it gets wiped out as shown above for the first item within quicklinks.
Has anyone seen this before or have any ideas we could try?
is working on a reply...