12

Technically the message is right - there is no Content Porter Server installer anymore, this is now included in the standard Content Manager Core. But the client installer is not included in the CM Core (long story short: we couldn't finish the client in time for the 2013 SP1 release). So you still need to run an installer (you can get it from Customer ...


8

I believe this was possible since 2013? You can port custom appdata as long as you follow a convention. Experience Manager, Translation Manager, DXA and others use this mechanism. I thought this was documented, but can't find the reference to it right now. If you look under [Tridion]\config\ImportExport\ApplicationData you'll find a bunch of xml files with ...


8

In SDL Tridion 2013 (SP1), the same error persists when you try to send the same structured content via the Translation Plugin. To fix (in Translation Manager) we used the hotfix TT87682 part of the TM package here. We successfully content port our content, with this same scenario - our versions are: from SDL Tridion SP1 HR1 to SDL Tridion SP1 using ...


7

The ReleaseManager extension is actually only intended to be used to "bundle" a group of Tridion items for a release. The way that it actually works is that it stores all items added to the release in an XML file which is maintained on the filesystem (I've also seen it adapted to be stored in AppData). When you use the ReleaseManager extension to generate ...


6

Three options you may want to consider: Rename the BPT in the source system (to the same name as the one used in the destination) before doing the export and then just exclude it from the import, to ensure that it's not updated. Use the Mappings file to change the name (WebDav path) of the BPT during the import. More details in the Changing mappings section ...


5

Besides everything Jonathan said in his answer, I would like to clarify a bit what is the purpose of Content Porter and how it works. It is used for transferring mainly components, templates or pages to ease out the DTAP deployment. What is more important, during import/export current security model on server is applied. So in your case, you would try to ...


5

It looks like this is an error in the documentation. The Non-exportable items page lists the items that will not be included in the Content Port. This list includes: Permissions for Publications, Folders, and Structure Groups However, permissions are not ported between environments for any ‘organisational item’. This includes Categories. Therefore, I ...


4

Note also that you will not need a Content Porter license when running Content Porter 2013 SP1 on a Tridion 2013 SP1 system.


4

I ran into this problem today. In my case, I was selecting the application data category "User Generated Content." or as referenced in the error, ugcComponentAndPage. I did not need to select this category for my export. So, I went through the content porter export steps again, this time not selecting user Generated Content and my export completed without ...


3

Run ttm-prepare.ps1 which comes in your DXA package and it will preconfigure the Topology Manager for the DXA Site Type and Business Process Types.Also Please check Topology Manager is installed properly in IIS and its CMDLET commands click here are available.


3

Two approaches you might consider Clone the database from Server A to Server B. Then change the few environment specific items (e.g. Publication Targets) and remove / delete anything you did not want to Port Make several smaller Content Ports (via API or manually), normally ordered by type lowest to highest (e.g. Folders & Structure Groups, then Schemas,...


3

Welcome to the Tridion community! The Release Manager extension is quite old. It was excellent back in the day, but today we have Bundles with Tridion. To directly answer your question, no, you will not have that same release in another environment after Content Porting. All Release Manager does is creates an Export XML file that you can load into Content ...


2

Since 2013 SP1 Content Porter Core part is placed in Tridion Core (TcmServiceHost + IIS). Your stack trace shows, that there is problem on creating session (impersonation). Look here http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-20723F2E-686D-44AC-835A-8F84A5DD7A22#url=/LiveContent/web/search.xql%3Fc%3Dt%...


2

Did you configure the steps needed for Content Porter configuration with LDAP? Please check the Tridion docs and follow these steps : http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL%20Content%20Porter%20full%20documentation-v1/GUID-3AB5898C-743B-4B4B-BE8B-46F1C0CDD300 Please note, these are additional steps needed for Content Porter in addition ...


2

Have a look at the SynchronizeFlags enum. You're using synchronizeFlags.All and that does more than you need to get valid content. For example: putting default values in optional fields. That is exactly what the TM hotfix is about: avoid the use of SynchronizeFlags.All, but only use the flags that will fix validation issues.


2

Before you can import DXA you need a fully operational content delivery environment, as described here This means you first need to setup the CD and Topology. The import is failing as it cannot find any CdTopologyTypes. If I recall correctly, you can use the `quickinstall' PowerShell script to setup a basic Topology. A quick summary of doing this manually ...


2

I eventually found the answer to this in the Configuring this import page of the Content Porter online documentation: If you are importing into SDL Tridion 2013 Content Manager or older, under Do you want to update dependencies, select one of the following: Select Yes if you want Content Porter to always perform an update of a dependency if ...


2

When you are exporting, it's likely you're not exporting dependencies. And there is a dependency that is required (which may be the item referred to above - or could be something deeper in the list) - you'd need to sanitise/share the full log). You could try with a single component (with a single simple text field - no links, keywords etc.) in the root ...


1

As Velu says, you can script the export and import of "content porter" packages via the Import/Export service API. Essentially, all the core functionality of Content Porter has gradually moved to the server, and the Content Porter client is just user interface. Things that were tricky using the client don't magically become easy with the service, but it can ...


1

Just my thought and idea, I think OOTB - you could think of writing a PowerShell Automation script to import your packages using ImportService and then link that script to your CI/CD Deployments, It's still possible whatever we do in our content porting options you could able to achieve using core services. One time any way you need to prepare that ...


1

After going through the documentation Content Porter for SDL Web 8 I found missing prerequisites. Once all the prerequisistes (VC++ 2010 x86, Microsoft.NET 4.5.2) were installed I was able to get the Content Porter Icon and it was working fine.


1

I would like to clarify a bit the response Mark has gave you. He is completely right. Basically, when you export bundle, you don't export single item. You export virtual folder with references to items. What it means? Basically, you say to Tridion: Export everything in this group, so each item is treated differently, and each item has its own dependencies. ...


1

XLinks in custom content/metadata are "managed" by CM Kernel. Meaning: if such XLinks contains a TCM URI or WebDAV URL of a CM Component, a managed Component link will created (which shows up in Where Used and prevents the linked Component from being deleted). This also allows you to request the XLink as TCM URI or WebDAV URL (regardless of how it was saved)....


1

I agree with the two suggestions that Chris has made in his answer. I guess that the approach depends on whether you need to delete any content (and if so, then how much!) following a database clone. Another alternative, if you want to go down the Content Porting route (and be able to 'cherry pick' the content to move) would be to use the Import Export ...


1

Based on my experience with content porter, it is very helpful tool for small porting however not a good tool for very large data like yours. Since your one instance is Amazon AWS, I assume you are on web 8. For your there are two alternatives: If you are on web 8 with web 8 type publishing with topology manager then database clone is the fastest ...


1

Review the following link where Brandon added some extra comments that might be usefull for you http://docs.sdl.com/LiveContent/content/en-US/SDL%20Content%20Porter%20full%20documentation-v1/GUID-7B19341C-7E20-48BA-BAB0-46E3D3D84469


Only top voted, non community-wiki answers of a minimum length are eligible