Data loss as we do Migration to new layouts using a script

manubhai

Hi All,

We are migrating existing .page from two column layout (fixed) to three column layout(fixed) using a Script.These are the steps which we following :

1.Create a new three column layouts and submit the layout.
2.Create a new template using three column layout (created in step1), add components which were part of existing template(2column).
3.Download all pages which need to be update with three column layout.
4.Execute the java based script on the downloaded pages to update, this script will do the following task:
a.Replaces the template name, version(set version to 1) and vpath with newly created template (three column layout).
b.Replaces layout name and canvas path with newly created three column layout.
c.Replaces selected skins for components (if required).
d.Replaces the components area id of old layout with the area id of new layout.
5.Once script is done, upload modified pages to team site.
8.Go to template folder, open template in edit mode save and submit it so that it can make version 2 of these templates which is required for get latest process.
9.Now perform the get latest for pages which will update the templates with latest version.

All these steps above successfully do migration to three column layout.But the issue is that ,there is a data loss on the pages for the components part of the template.Any pointers how we can prevent data loss.

Rick Poulin

Go to template folder, open template in edit mode save and submit it so that it can make version 2 of these templates which is required for get latest process.

Why didn't you just set the version to 0 when you're updating the XML?

All these steps above successfully do migration to three column layout.But the issue is that ,there is a data loss on the pages for the components part of the template.Any pointers how we can prevent data loss.

Please realize that what you're doing is very much unsupported, so data loss is something you might just have to live with. That said, there's probably a fix for this but your summary doesn't inspire confidence that you actually understand the purpose and use of all parts of the XML structure. In particular, you mentioned nothing about updating template and component IDs, which probably has a lot to do with your data loss when you 'get latest'. (they're not just magic numbers for uniqueness and looking fancy)