-3

I have an issue with content within a Component Presentation not being displayed on a published page.

I can see the content when I Preview the Component Presentation, and when I Preview the Page, within the Tridion CME. Also, I see the content of the Component Presentation when running this through Template Builder. However, the content within the Component Presentation is not shown on the published page.

The Page is getting published successfully. It shows the HTML from within the Page Template's Dreamweaver Template (DWT) - The only thing missing is the content of the Component Presentation, which I assume means that this is not getting rendered on the published page somehow.

The Page is static, it's not using any Dynamic Component Presentations.

Am I missing something?

10
  • You'll need to provide some more information here as to how you're publishing the content / storing it &c.
    – johnwinter
    Apr 3 '14 at 16:39
  • We are publishing the content from CMS to CDA and both are on different AWS servers. We have used Default finish actions. ARe we missing anything over here or let me know what else information should I provide you?
    – user918
    Apr 3 '14 at 16:42
  • i'm sorry but that's not very detailed, i think you've a lot of gaps missing in your SDL knowledge here, it might be worth you looking at the documentation (sdllivecontent.sdl.com/LiveContent/web/pub.xql) to read the chapters on publishing and content delivery
    – johnwinter
    Apr 3 '14 at 16:48
  • How are the components added to the page? Are these dynamic Component Presentations? Where are they stored? Which type of DCPs? Try making them "Embedded CPs" first.
    – Nuno Linhares
    Apr 3 '14 at 16:53
  • John, let me give you some more information. I have published a page, the page is getting published, and its having the DWT HTML code part. Only thing missing is the content of the component which means the component is not getting rendered on the page.
    – user918
    Apr 3 '14 at 16:54
3

This type of behavior typically occurs when your Component Template is set to dynamic, but your Content Delivery environment and/or Pages are not setup correctly.

For instance, your pages could be using the .html extension, which (by default) will not execute server-side code. Since DCPs get added to the pages on the server-side, the content will not be loaded if your extension is .html. A clear sign that this is happening is that you'll see tags like this:

<tridion:ComponentPresentation [...] />

in your page source in the browser.

Another possible reason is that your Publication Target is configured to use "Language: None", which means that Tridion can't create the required Content Delivery API calls to load your Dynamic Component Presentations.

Yet another possible reason is that you configured your Component Templates to use output format "Jsp" or "Ascx" but didn't configure it properly in your cd_storage_conf.xml on the delivery side.

And the list goes on and on. Adding more detail (for instance, covering the examples I mentioned above) will help us help you.

UPDATE

Just want to mention one of the comments added to this thread by Alvin: Can you make sure your Page and Component Templates are correctly checked in in Tridion? Preview and Template Builder will use the latest version of those templates, but the publisher will only use checked in versions.

16
  • Thanks Nuno, will check all these key points mentioned by you and will let you know in case these might not be the case.
    – user918
    Apr 3 '14 at 17:05
  • Check this answer if this is what Nuno mentioned above: tridion.stackexchange.com/questions/4986/… Apr 3 '14 at 17:13
  • we don't have any dynamic cps. we hv only embedded cps.
    – user918
    Apr 3 '14 at 17:17
  • Weird then. Can you verify they are in the page content (the published file)?
    – Nuno Linhares
    Apr 3 '14 at 17:20
  • 1
    @Nash don't respond to a comment by adding code, that is not readable and not useful. Edit the question if you have more information to add. In a question you can also properly format any code added which makes it readable. I suggest you delete your comments with code here and add all that information in the question. Apr 4 '14 at 8:32
2

As you answer, you did not do any custom templating code and just use the Default Finish Action TBB.

Assuming:

1.you are using Tridion supplied “Default Finish Action TBB” on the page.

2.In CT you have written proper code to render the content of the Component.

Now, I don’t think the “Default Finish Action TBB” will render any content for you.
Check the details about this TBB here (Login Required)

So you need to add a TBB to the Page Template, which renders the component presentations on the page.

Of course you can do the component presentation preview on the page as PT has no role in it and only CT is used to display the output (though, I am still surprised you are getting the preview for the page)

Please add a TBB (to render ComponentPrasentations) on the Page Template like a DWT TBB having code like below:

<!-- TemplateBeginRepeat name="Components" -->
@@RenderComponentPresentation()@@
<!-- TemplateEndRepeat -->

I hope, this helps.

4
  • we are not using any templating except the default finish action TBB's, and preview is working fine for both CP and page.
    – Nash
    Apr 3 '14 at 18:00
  • Can you confirm that the expected content is not present in the published file? Apr 3 '14 at 18:03
  • yes its not present in the published file as i confirmed by opening that file in notepad.
    – Nash
    Apr 3 '14 at 18:12
  • 1
    On the other comment thread you said the content WAS present in the published file... I suggest you move this discussion to the chat channel and we stop polluting this question
    – Nuno Linhares
    Apr 3 '14 at 18:58

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.