Timeline for Moving components/folders from child publication to parent publication without breaking its dependencies
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2014 at 17:58 | comment | added | Alvin Reyes | Update: Anton Minko demystifies the mapping file: tridioninternals.blogspot.com/2014/02/…. I take back my "not that fun" comment. :-) | |
| Nov 15, 2013 at 5:17 | comment | added | Alvin Reyes | The hardest part of using the Mapping.xml is likely the encoding and choosing the right paths. I've done it (but it's not that fun). Exporting pages would actually be a good idea, that way you can copy them from below when done, rather than having to re-wire them. The move part after the export is important (otherwise CP will complain about the path conflict). Start with a single page and its components to test, you'll be fine. | |
| Nov 13, 2013 at 13:04 | vote | accept | Patan | ||
| Nov 13, 2013 at 11:38 | history | edited | johnwinter | CC BY-SA 3.0 |
added 204 characters in body
|
| Nov 13, 2013 at 11:37 | comment | added | johnwinter | potentially export pages and components as two different exports, if you can remove the pages, then fix issues with components, the re import the pages, ensuring the component dependencies are correct. - very tricky and be very careful of how you achieve this. | |
| Nov 13, 2013 at 11:09 | comment | added | Patan | Thank you for answer. If the components are used in pages, in that I also need to import and export pages also right. | |
| Nov 13, 2013 at 10:48 | history | answered | johnwinter | CC BY-SA 3.0 |