I've done a fair few upgrades now and I make use of PhoenixConvertors for which I've had to develop some of my own but the project does have a Legacy MNTP to MNTP convertor out of the box which is what you will likely need to migrate the legacy data.
Hi Simon, thanks for that - I created a manual process in the end - her it is for anyone interested:
First, get affected nodes as XML:
select '<r id="' + cast(id as nvarchar(10)) + '">' + cast(dataNtext as nvarchar(max)) + '</r>'
from cmsPropertyData where dataNtext like '%MultiNodePicker%'
Wrap the above in <root></root>.
Use an XSL tool to transform to an update statement:
update cmsPropertyData set dataNvarchar= '3026' where id = 50233
update cmsPropertyData set dataNvarchar= '3027,3028' where id = 50234
NOTE 1: You may have to run the again for the cmsPropertyData.dataNvarchar field to get them all.
NOTE 2: This is for the OBSOLETE node picker, but no reason you couldn't modify the SQL in the transform to get the guid for the new style storage.
The above technique also works with the old MultiUrlPicker - use this transform to convert link info into plain html links separated by line breaks - modify for plain text / markdown or whatever.
Upgrading 4.11 to 7.7.2 - MultiNodePicker
I am upgrading an old 4.11 site, which uses the uComponents MultiNodePicker.
This does not carry across to the new version, so I selected the
Umbraco.MultiNodeTreePicker (Obsolete)
thinking that this would be the replacement.Trouble is, it does not load the existing stored values into content.
I get the following error in the log:
The old values are persisted as XML, of course - does the new picker not load that? Is there any way around this - I have a lot of fields to migrate!
I've done a fair few upgrades now and I make use of PhoenixConvertors for which I've had to develop some of my own but the project does have a Legacy MNTP to MNTP convertor out of the box which is what you will likely need to migrate the legacy data.
https://github.com/imulus/PhoenixConverters
Hi Simon, thanks for that - I created a manual process in the end - her it is for anyone interested:
First, get affected nodes as XML:
Wrap the above in
<root></root>
.Use an XSL tool to transform to an update statement:
This should give you something like:
NOTE 1: You may have to run the again for the
cmsPropertyData.dataNvarchar
field to get them all. NOTE 2: This is for the OBSOLETE node picker, but no reason you couldn't modify the SQL in the transform to get the guid for the new style storage.The above technique also works with the old MultiUrlPicker - use this transform to convert link info into plain html links separated by line breaks - modify for plain text / markdown or whatever.
NOTE: This only gets the link url and title as that's all I need; you can get target etc easily enough though.
is working on a reply...