15

To avoid overloading the CM server with heavy import/export jobs, there is a configurable cap on the number of import/export processes that can run concurrently. The default configuration allows only one concurrent process, but this can be changed in Tridion.ContentManager.config EDIT (Nuno) Couldn't find any documentation, but this is the setting you want ...


11

Chrome has an extension to launch ClickOnce applications. It includes a mime type mapper that will correctly launch x-ms-applications when a link to a .application is clicked. You can find it here: https://chrome.google.com/webstore/detail/clickonce-for-google-chro/eeifaoomkminpbeebjdmdojbhmagnncl?hl=en Adding that will allow you to open the Template ...


10

Yes, you certainly can use bundles for Content Porter Export... unfortunately, the current version of Content Porter will export the items from the same publication that you're exporting the bundle from... so not extremely useful. As from 2013 SP1 (coming out soon) you'll be able to tell Content Porter to export the items in a bundle from their Parent (or ...


9

As you say, SDL Tridion 2013 SP1 now comes with the Import/Export Webservice as part of the Core Content Manager (CM) installer. Running the Content Porter 2013 SP1 installer against an Tridion 2013 SP1 Content Manager just makes the Content Porter client icon available within the Tools menu, and does not install any additional functionality. The Import/...


9

Have manged to resolve the issue The CMS server(x64bit) had Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 Installed For CP 2013SP1 it needs Microsoft Visual C++ 2010 x86 else CP on the server gives above noted error. After installing the VC++ x86 it works like a charm. Sharing here for the rest of the CP lovers :) Thanks Vin


9

In this case the z_Test_Client_Information.xml component failed to import because /webdav/030%20Content/Building%20Blocks/Content/z_test_content/z_test_folder doesn't exist. This item doesn't have an extension and so it is a folder. Once the folder is created in the destination environment (either by importing it or by creating it directly), your import ...


8

This is due to the (optional) management of dependencies that is a feature of the Razor Mediator. If (in Tridion.ContentManager.config) you set the includeConfigWhereUsed attribute to true in the Razor configuration section then every Razor TBB you subsequently create or edit will have a dependency on Razor TBB(s) set to globally import in the imports ...


7

You've listed the typical approaches I've seen. Though with cloud options you might add a fourth. I'm personally seeing testing done on separate branches of entire (all-in-one) environments. This might not apply to most Production setups, though. The documentation (requires login) confirms your thoughts in terms of: DTAP - Dev, Test, Acceptance, and ...


7

Tridion 2013 does have a specific bundle management right (per publication, just like the other rights such as page management, component management etc.) However, I don't think that will help you. Bundles are a type of virtual folder (similar to a search folder) and the items contained within them are regular Tridion items with a location elsewhere in the ...


7

I can confirm that the import will fail if you try to move legacy items to a CM server without a legacy pack installed. It is possible to skip importing these items, but this will cause a bunch of dependency failures on following imports. Sadly, unless you're willing to modernize your existing content, the legacy pack is required to import content from 2011 ...


7

The answer is in the error message: If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'. WCF never allows to have two endpoints in a service model configuration ...


7

The only option that we've found working is by separately exporting and importing the stubs from the parent publication before exporting and importing the other items. Disclaimer: I don't know if this is the right way to do it, but as said, it seems to be the only option.


7

Content Porter (or more general: the CM Import/Export service) triggers the same events as when the same actions were performed on the TOM.NET API directly, but it does set Session.ContextData so that event handlers can detect that the events are triggered by an CM Import (or Undo) action. Note that this is true for Tridion 2013 SP1 and higher (earlier ...


7

As Nuno mentioned, CP for Web 8 is not released yet. And CP 2013 SP1 officially doesn't support Web 8, so officially you can't use CP for that purpose yet. But, indeed, for DXA 1.3 (which is also not released yet) we're using a 2013 SP1 CM Import/Export client to import in both 2013 SP1 and Web 8 without any issues. As a matter of fact, we even use the 2013 ...


7

Unfortunately not. The following description is given in the Export constraints section of the online documentation: Items in workflow You cannot export a version of an item that is in workflow, not even if the item is assigned to the user who is performing the transfer. Instead, the version that will be exported is the last version that ...


6

I'd look into configuration first, specifically for Multimedia Types for Zip and JPEG (because of the .tmt extension). It might not be the package itself (these typically export fine), but what's missing in the destination environment. I'd expect JPEG to be out-of-the-box per SDL Live Content (requires login), though.


6

Get to a point when all Dev is stopped and deployed to Prod, so that Prod has latest code and content. Then do a DB clone from Prod back to Dev. When you do this, you'll need to update the publish target configs, possibly your list of users and set all the content to unpublished. For small amounts of content use Content Porter.


6

This is how I would go about resolving this: Write a CoreService app that looks through every component searching for fields containing a TcmUri; Convert that TcmUri to a WebDavUrl by loading the target object and getting it's WebDavUrl (some smart caching suggested here) Save/Update the components (probably before step #1) make sure my code still works ...


6

You can export Group but not their permission settings (on organizational items). SDL Docs lists the following non-exportable items: Font definitions Protocol Schemas in publishing Schemas in publishing (I'm not sure what this means, actually) Target types in publishing Publication Targets in publishing Page and Component publishing status Users Security ...


6

Have you checked the documentation? You can use explicit transfer mappings: https://docs.sdl.com/LiveContent/content/en-US/SDL%20Content%20Porter%20full%20documentation-v1/GUID-2587308B-86CB-4AA2-BDA3-E740A1349418 if this is a permanent situation then you would likely follow this route as you can save out to config Or you could even consider temporarily ...


5

The online documentation (login required) highlights a number of items that are 'non-exportable' when using Content Porter: An export cannot export the following items: Font definitions Protocol Schemas in publishing Schemas in publishing Target types in publishing Publication Targets in publishing Page and Component publishing status ...


5

This error occurs when you try to save an element of the same name and location (webdav path) in a parent publication and it already exists in a child publication. The item physically cannot saved (imported) because of the naming conflict in one of the child publications. I'd check the content porter log to find out the actual item in question and review ...


5

You'll have to load the component as XML, and update/read as XML too. ItemFields will always try to load some of the properties of the linked component when it is initialized, and that means it will fail (as you have noticed already). tcccp:unresolved means that for some reason the target of that link was not found (or failed to import if it was part of the ...


5

You mention you have SDL Tridion version 2011 SP1 and you are trying to install Content Porter 2013. As listed in its release notes, Content Porter 2013 will work on the following SDL Tridion CMS versions: 2009 SP1 2011 SP1 Hotfix Release 1 (aka. 2013 SP1 HR1) 2013 So the error you got while trying to install Content Porter 2013 was correct, you seem to ...


5

You can Content Port from earlier versions of Tridion in to SDL Tridion 2013 SP1 - I did this recently, between Tridion 2011 SP1 HR1 and Tridion 2013 SP1. One thing to note is that you will need the Content Porter 2013 SP1 Client to be able to import in to SDL Tridion 2013 SP1. Although SDL Tridion 2013 SP1 now comes with the Import/Export Webservice as ...


5

Unfortunately, there is no mechanism in Content Porter for setting the ID's of newly created items (including Publications). The ID is auto-generated each time and just incremented (from the last used ID). Writing code that relies on fixed ID's is bad practice in Tridion. If possible, I'd recommend that you use WebDAV paths, or have a configuration file ...


5

maxAllowedContentLength matters because, your package is first uploaded on CMS machine, then import starts. i don't think timeout will differ as Package and ImportExportService exists on the same server in both cases.


5

There is an extension you can try called the Release Manager: http://sdltridionworld.com/community/2011_extensions/Releasemanager.aspx. It allows for tagging an item in Tridion for a release and then creates the export xml file based on the tagged list of items. Another option is to use Tridion 2013 Bundles. Will Price wrote about that here: http://www....


5

Yes they do. That is: it is possible to let the client tools connect to the CM server through an SSO proxy. Prerequisite for such a configuration is that the SSO proxy uses HTTP basic auth for those endpoints One could argue that is hardly a SSO experience, but that is as far as it goes currently.


5

You should be able to use a mappings.xml file to transform the XmlName during the import, rather than hacking the Content Porter export. According the online documentation, the mappings file allows you to: handle items that were renamed on the source system or on the destination system after a transfer ...Which seems to fit your scenario. Within the ...


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