9

We have 03 main publication and then 04a,04b,04c,04d translated publication . Our requirement is to copy all translated content from 04a and copy into 04e at same level. Can we do this through content porter . Where all i need to change mapping.xml to do this.

I have a idea to change the webdev path of intermediate package to point 04e and import it.

Please suggest .

  • This sounds like it would be better Blueprinted, i.e. 04e using 04a as a parent publication? If not, what are you trying to achieve with the copy (i.e. once copied, what changes will be made to the content?) – Dave Forber Jul 16 '13 at 15:15
12

As it is not possible to copy across publications, Just By renaming the publications for your operations you can do this. Mapping xml is also the option for this but renaming seems to be more comfartable.

1.Rename 04a --> temp
2.Create Content Porter Package
3.Rename temp --> 04a
4.Rename 04e --> temp
5.Import package in to temp
6.Rename temp -->04e

For Editing of Mappings XML click on highlighted Edit button which will open the mappings XML. You need to update importContext and importTitle attributes in this file which are by default empty. I would suggest the renaming of publication as it is less error prone. enter image description here

| improve this answer | |
  • Alok,Can you share the mapping.xml details as well because 04a is inherited by 10 more publications at 07 level...so it will be a very big risk to do that . – Jitender sharma Jul 15 '13 at 10:50
  • I have tried editing the mappings xml once but got errors while porting. So you need to work out how to correctly update mappings xml – AlokBhatt Jul 15 '13 at 11:05
  • Alok,this mapping open a temporary file in temp folder.I am talking about the mapping file in intermediate package . – Jitender sharma Jul 15 '13 at 12:59
  • 1
    +1 on renaming before import or export approach - I've used this one in the past quite successfully – Nuno Linhares Jul 15 '13 at 14:03
  • 1
    there is never a risk in renaming a Publication, unless you have some functionality which depends on that name. Renaming a Publication temporarily for export/import purposes will have no effect what so ever on any of your other Publications. – Bart Koopman Jul 16 '13 at 9:37
2

I agree the rename is easier. Editing mappings.xml doesn't seem to be popular in my SO answer, but also see post from Monica Manzano and a rant from Dominic Cronin also describing the renaming approach.

Mappings.xml

The mappings.xml file is documented on SDL Live Content for recent Content Porter versions.

Format

Note the URL-escaped paths in the following example (Content Porter 2009 up to SP1):

<tcccp:Mapping
  exportContext="/Publication/Building%20Blocks"
  exportTitle="component.xml"
  importContext="/Destination%20%Pub"
  importTitle="" />

IMO, it's worth doing the "official" way at least once (then we could get feedback to the right people). :-)

Edit: formatted XML into separate lines. My mappings.xml had this on one line.

| improve this answer | |
  • That was a pretty good rant, too... back in 2008. :-) – Dominic Cronin May 20 '15 at 7:10
1

You're probably better off with looking into a blueprint solution, but the trick is to rename publication 4a into "temp port pub", do the export, undo the publication name change, now change 4e into "temp port pub", do the import, and undo the publication name change.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.