Porting content the efficient way!
Is it possible to have a packet with all components and pages in export package and then just importing all the pages(which should automatically be resolving all the missing reference as all components are already there in the package) ?
I just tried the traditional way, which is first exporting the component and then the pages. Well lets just say that it is taking forever to resolve dependencies, and separately importing localized version.
Also what steps I can follow to have all the localized versions of both component and pages as well?
content-manager content-porter-2013
add a comment |
Is it possible to have a packet with all components and pages in export package and then just importing all the pages(which should automatically be resolving all the missing reference as all components are already there in the package) ?
I just tried the traditional way, which is first exporting the component and then the pages. Well lets just say that it is taking forever to resolve dependencies, and separately importing localized version.
Also what steps I can follow to have all the localized versions of both component and pages as well?
content-manager content-porter-2013
add a comment |
Is it possible to have a packet with all components and pages in export package and then just importing all the pages(which should automatically be resolving all the missing reference as all components are already there in the package) ?
I just tried the traditional way, which is first exporting the component and then the pages. Well lets just say that it is taking forever to resolve dependencies, and separately importing localized version.
Also what steps I can follow to have all the localized versions of both component and pages as well?
content-manager content-porter-2013
Is it possible to have a packet with all components and pages in export package and then just importing all the pages(which should automatically be resolving all the missing reference as all components are already there in the package) ?
I just tried the traditional way, which is first exporting the component and then the pages. Well lets just say that it is taking forever to resolve dependencies, and separately importing localized version.
Also what steps I can follow to have all the localized versions of both component and pages as well?
content-manager content-porter-2013
content-manager content-porter-2013
asked 7 hours ago
Bhawna JainBhawna Jain
280114
280114
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I'd question the work 'just' in your post.
When you say
all components and pages
then the quantity and complexity very quickly becomes a core question.
Also, I'd suggest it's important to make the point here that it doesn't automatically mean the tool is at fault just because a process takes a long time (although I accept it would be much more useful if we had better/any visibility of that CP was doing at any point in time).
Content Porter (and with that, I mean the associated ImportExport Service) is performing some pretty complex checks when resolving dependencies; not just checking if a component needs including as it's on a page - but (depending on your settings), the schemas being used, that the fields in the component XML match to the schema fields at that point in time and much much more)
How complex is your content model for the items your are importing/exporting?
What's the level of localization?
What the complexity of the Blueprint structure?
What items are you asking Content Porter to dependency check?
If you're looking to move from Content Porter to an app utilising the ImportExport service you're still going to have to understand the content you're moving to best understand how to help the service work most efficiently.
I often find that it real-world scenarios a client will expect you to truly understand the content/assets you are moving through Content Porter and expect you to manage the dependencies - thus allowing you to create a port for Keywords, Schemas, Components and then Templates and then Pages etc.
I'd suggest posting some of your Content Porter settings, perhaps indicate what amount of content you're pushing and the level of nesting within it etc. Then we may be able to spot some simple, quick fixes to assist.
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
add a comment |
Yes and yes. You can use ImportExport service to export data the way you need it and import also. Please make notice that content porter in background connects to same service. The advantage here is that you can automate activities like exporting pages based on criteria and impprting them in bulk or in steps. But good thing is that tool does it for you.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "485"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19879%2fporting-content-the-efficient-way%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'd question the work 'just' in your post.
When you say
all components and pages
then the quantity and complexity very quickly becomes a core question.
Also, I'd suggest it's important to make the point here that it doesn't automatically mean the tool is at fault just because a process takes a long time (although I accept it would be much more useful if we had better/any visibility of that CP was doing at any point in time).
Content Porter (and with that, I mean the associated ImportExport Service) is performing some pretty complex checks when resolving dependencies; not just checking if a component needs including as it's on a page - but (depending on your settings), the schemas being used, that the fields in the component XML match to the schema fields at that point in time and much much more)
How complex is your content model for the items your are importing/exporting?
What's the level of localization?
What the complexity of the Blueprint structure?
What items are you asking Content Porter to dependency check?
If you're looking to move from Content Porter to an app utilising the ImportExport service you're still going to have to understand the content you're moving to best understand how to help the service work most efficiently.
I often find that it real-world scenarios a client will expect you to truly understand the content/assets you are moving through Content Porter and expect you to manage the dependencies - thus allowing you to create a port for Keywords, Schemas, Components and then Templates and then Pages etc.
I'd suggest posting some of your Content Porter settings, perhaps indicate what amount of content you're pushing and the level of nesting within it etc. Then we may be able to spot some simple, quick fixes to assist.
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
add a comment |
I'd question the work 'just' in your post.
When you say
all components and pages
then the quantity and complexity very quickly becomes a core question.
Also, I'd suggest it's important to make the point here that it doesn't automatically mean the tool is at fault just because a process takes a long time (although I accept it would be much more useful if we had better/any visibility of that CP was doing at any point in time).
Content Porter (and with that, I mean the associated ImportExport Service) is performing some pretty complex checks when resolving dependencies; not just checking if a component needs including as it's on a page - but (depending on your settings), the schemas being used, that the fields in the component XML match to the schema fields at that point in time and much much more)
How complex is your content model for the items your are importing/exporting?
What's the level of localization?
What the complexity of the Blueprint structure?
What items are you asking Content Porter to dependency check?
If you're looking to move from Content Porter to an app utilising the ImportExport service you're still going to have to understand the content you're moving to best understand how to help the service work most efficiently.
I often find that it real-world scenarios a client will expect you to truly understand the content/assets you are moving through Content Porter and expect you to manage the dependencies - thus allowing you to create a port for Keywords, Schemas, Components and then Templates and then Pages etc.
I'd suggest posting some of your Content Porter settings, perhaps indicate what amount of content you're pushing and the level of nesting within it etc. Then we may be able to spot some simple, quick fixes to assist.
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
add a comment |
I'd question the work 'just' in your post.
When you say
all components and pages
then the quantity and complexity very quickly becomes a core question.
Also, I'd suggest it's important to make the point here that it doesn't automatically mean the tool is at fault just because a process takes a long time (although I accept it would be much more useful if we had better/any visibility of that CP was doing at any point in time).
Content Porter (and with that, I mean the associated ImportExport Service) is performing some pretty complex checks when resolving dependencies; not just checking if a component needs including as it's on a page - but (depending on your settings), the schemas being used, that the fields in the component XML match to the schema fields at that point in time and much much more)
How complex is your content model for the items your are importing/exporting?
What's the level of localization?
What the complexity of the Blueprint structure?
What items are you asking Content Porter to dependency check?
If you're looking to move from Content Porter to an app utilising the ImportExport service you're still going to have to understand the content you're moving to best understand how to help the service work most efficiently.
I often find that it real-world scenarios a client will expect you to truly understand the content/assets you are moving through Content Porter and expect you to manage the dependencies - thus allowing you to create a port for Keywords, Schemas, Components and then Templates and then Pages etc.
I'd suggest posting some of your Content Porter settings, perhaps indicate what amount of content you're pushing and the level of nesting within it etc. Then we may be able to spot some simple, quick fixes to assist.
I'd question the work 'just' in your post.
When you say
all components and pages
then the quantity and complexity very quickly becomes a core question.
Also, I'd suggest it's important to make the point here that it doesn't automatically mean the tool is at fault just because a process takes a long time (although I accept it would be much more useful if we had better/any visibility of that CP was doing at any point in time).
Content Porter (and with that, I mean the associated ImportExport Service) is performing some pretty complex checks when resolving dependencies; not just checking if a component needs including as it's on a page - but (depending on your settings), the schemas being used, that the fields in the component XML match to the schema fields at that point in time and much much more)
How complex is your content model for the items your are importing/exporting?
What's the level of localization?
What the complexity of the Blueprint structure?
What items are you asking Content Porter to dependency check?
If you're looking to move from Content Porter to an app utilising the ImportExport service you're still going to have to understand the content you're moving to best understand how to help the service work most efficiently.
I often find that it real-world scenarios a client will expect you to truly understand the content/assets you are moving through Content Porter and expect you to manage the dependencies - thus allowing you to create a port for Keywords, Schemas, Components and then Templates and then Pages etc.
I'd suggest posting some of your Content Porter settings, perhaps indicate what amount of content you're pushing and the level of nesting within it etc. Then we may be able to spot some simple, quick fixes to assist.
answered 4 hours ago
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
7,3181232
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
add a comment |
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
yeah, in most cases editors just select export everything and then complain why it takes long. like exporting thousand of pages and components is fast :D
– Marko Milic
4 hours ago
add a comment |
Yes and yes. You can use ImportExport service to export data the way you need it and import also. Please make notice that content porter in background connects to same service. The advantage here is that you can automate activities like exporting pages based on criteria and impprting them in bulk or in steps. But good thing is that tool does it for you.
add a comment |
Yes and yes. You can use ImportExport service to export data the way you need it and import also. Please make notice that content porter in background connects to same service. The advantage here is that you can automate activities like exporting pages based on criteria and impprting them in bulk or in steps. But good thing is that tool does it for you.
add a comment |
Yes and yes. You can use ImportExport service to export data the way you need it and import also. Please make notice that content porter in background connects to same service. The advantage here is that you can automate activities like exporting pages based on criteria and impprting them in bulk or in steps. But good thing is that tool does it for you.
Yes and yes. You can use ImportExport service to export data the way you need it and import also. Please make notice that content porter in background connects to same service. The advantage here is that you can automate activities like exporting pages based on criteria and impprting them in bulk or in steps. But good thing is that tool does it for you.
answered 7 hours ago
Marko MilicMarko Milic
4,74121145
4,74121145
add a comment |
add a comment |
Thanks for contributing an answer to Tridion Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19879%2fporting-content-the-efficient-way%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown