Take the 2-minute tour ×
Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It's 100% free, no registration required.

I have created a Content Type for the PT of my Page based on a Schema and a Component Template.

In Experience Manager when I opt option to create and insert content on the Page then it creates the Component based on the Content Type, but it put that Component with some other Component Template (1st Component Template which is linked to that CT) not the CT used in the Content Type.

I have already configured the PT to use only predefined Content Types and there is only one Content Type.

Please suggest if this is the known bug in Tridion. I am using Tridion 2013-SP1 and working on a DD4T project.

Thanks. Mukesh

share|improve this question

2 Answers 2

There are basically two possible locations for Content Types. First the Page which you use as a Page Type, can contain so called cloneable Components (you specify in the Page whether to include the current Component Presentation or a copy of it). Secondly you can define Content Types on your Publication, these you can use in the XPM settings and add to a Page via that route.

I'm not really sure, but it sounds to me like you might have both options, so a Component on the Page with the first CT and then in the Publication properties a Content Type using the same Component but with a different CT.

Apparently when you define both, it will use the one on the Page as a preference. If you have no Component Presentations on your Page, then it sounds like a defect indeed.

share|improve this answer
    
Hi Bart, I have Page and content type both in my publication. My content type also have the correct CT(A). But when we opt option to create and insert content it insert the content with wrong CT(B). This wrong CT is 1st CT which have linked schema same as my component schema. I think this is the issue with experience manager insert content option.When I created a region on the page and drag the component to region then it insert the component with correct CT. But unfortunately when I remove all the content from page then region disappear and then dragging component cause wrong CT appearing. –  Mukesh Kumar Aug 6 at 13:54
    
@MukeshKumar the region should be on your Page, not created or related to content being on the Page. But that is besides the point, from that what I have seen myself is that it worked fine when there was a cloneable Component directly on the Page. –  Bart Koopman Aug 6 at 14:34
    
Hi Bart, Yes, cloneable component with page type is working fine in my case too. Issue appears when I am trying to insert(either by create and insert or by adding existing component) any component from site edit UI. While I am dragging the component inside region, it is working fine and render with CT already used on the page but when there is no component available on page then it is inserting with other CT. Please suggest if I am missing something.. –  Mukesh Kumar Aug 6 at 15:04
    
@MukeshKumar when you drag and insert it will only follow region directions I think, so if you don't have the region markup specified, it will take the first available CT indeed. –  Bart Koopman Aug 6 at 15:41
1  
There is a subtle difference in behavior between Insert and Drag-and-drop. Regions change what we should do. The documentation notes to not use Insert with regions. I figured out why in this post. Without regions, then the "first template" applies (see @PeterK's answer). –  Alvin Reyes Aug 6 at 16:36
up vote 1 down vote accepted

I am just writing this answer to clarify confusion around content type and functionality of create and insert new content of experience manager.

When we create content type in a publication it has schema and CT associate with it with some other value too. When we create component for a webpage using specified content type from experience manager UI by selecting option create and insert new content we thought it will add the component with specified CT in content type but that is not actually happened and causes a confusion.

Clarification: Insert always insert the component with first CT it found in CMS. This is clarified by SDL documentation link and Alvin blog. Thanks again to Alvin to clarify this Tridion faulty behavior.

Thanks. Mukesh

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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