Return to Question

I understand that SDL Tridion will republish items that use an item you're publishing, which we might call "link propagation." We can change this behavior using Custom Resolvers or previously with the Event System.

AddBinary()

We can publish a multimedia component directly if it has a template associated with its schema. But we can also use AddBinary() to "implicitly" publish multimedia. Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it's removed.

RenderComponentPresentation()

Is this the same behavior, or even terminology, for RenderComponentPresentation()?

The docs explain (requires login):

If Pages include dynamic Component Presentations, dynamic Component Presentations are published. Pages on which the dynamic Component Presentation is used include a line of code that is be executed by the Content Distributor.

I'm guessing that "line of code" is RenderComponentPresentation() or an equivalent?

Do multimedia added with AddBinary or component Presentations with RenderComponentPresentations act the same in delivery? In other words, is the later also an implicit publish and are DCPs removed when no longer needed in delivery?

Background: I've seen questions related to link propagation (1, 2, 3, 4), but sometimes with phrases like "related items." I'm seeing the difference between the default resolving behavior, template logic that "publishes," but am not completely clear on delivery (yet). :-)

Update: On SDL Tridion 2011 SP1-1, I see:

• Queuing a page with an embedded component presentation where the component template is set to dynamic will also queue the DCP (visible in items to publish).
• A page with @@RenderComponentPresentation()@@ but no components won't show the referenced component in items to publish, but this DCP will show up in the broker database after a successful publish.

I understand that SDL Tridion will republish items that use an item you're publishing, which we might call "link propagation." We can change this behavior using Custom Resolvers or previously with the Event System.

AddBinary()

We can publish a multimedia component directly if it has a template associated with its schema. But we can also use AddBinary() to "implicitly" publish multimedia. Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it's removed.

RenderComponentPresentation()

Is this the same behavior, or even terminology, for RenderComponentPresentation()?

The docs explain (requires login):

If Pages include dynamic Component Presentations, dynamic Component Presentations are published. Pages on which the dynamic Component Presentation is used include a line of code that is be executed by the Content Distributor.

I'm guessing that "line of code" is RenderComponentPresentation() or an equivalent?

Do multimedia added with AddBinary or component Presentations with RenderComponentPresentations act the same in delivery? In other words, is the later also an implicit publish and are DCPs removed when no longer needed in delivery?

Background: I've seen questions related to link propagation (1, 2, 3, 4), but sometimes with phrases like "related items." I'm seeing the difference between the default resolving behavior, template logic that "publishes," but am not completely clear on delivery (yet). :-)

Update: On SDL Tridion 2011 SP1-1, I see:

• Queuing a page with an embedded component presentation where the component template is set to dynamic will also queue the DCP (visible in items to publish).
• A page with @@RenderComponentPresentation()@@ but no components won't show the referenced component in items to publish, but this DCP will show up in the broker database after a successful publish.

I understand that SDL Tridion will republish items that use an item you're publishing, which we might call "link propagation." We can change this behavior using Custom Resolvers or previously with the Event System.

AddBinary()

We can publish a multimedia component directly if it has a template associated with its schema. But we can also use AddBinary() to "implicitly" publish multimedia. Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it's removed.

RenderComponentPresentation()

Is this the same behavior, or even terminology, for RenderComponentPresentation()?

The docs explain (requires login):

If Pages include dynamic Component Presentations, dynamic Component Presentations are published. Pages on which the dynamic Component Presentation is used include a line of code that is be executed by the Content Distributor.

I'm guessing that "line of code" is RenderComponentPresentation() or an equivalent?

Do multimedia added with AddBinary or component Presentations with RenderComponentPresentations act the same in delivery? In other words, is the later also an implicit publish and are DCPs removed when no longer needed in delivery?

Background: I've seen questions related to link propagation (1, 2, 3, 4), but sometimes with phrases like "related items." I'm seeing the difference between the default resolving behavior, template logic that "publishes," but am not completely clear on delivery (yet). :-)

Update: On SDL Tridion 2011 SP1-1, I see:

• Queuing a page with an embedded component presentation where the component template is set to dynamic will also queue the DCP (visible in items to publish).
• A page with @@RenderComponentPresentation()@@ but no components won't show the referenced component in items to publish, but this DCP will show up in the broker database after a successful publish.

I understand that SDL Tridion will republish items that use an item you're publishing, which we might call "link propagation." We can change this behavior using Custom Resolvers or previously with the Event System.

AddBinary()

We can publish a multimedia component directly if it has a template associated with its schema. But we can also use AddBinary() to "implicitly" publish multimedia. Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it's removed.

RenderComponentPresentation()

Is this the same behavior, or even terminology, for RenderComponentPresentation()?

The docs explain (requires login):

If Pages include dynamic Component Presentations, dynamic Component Presentations are published. Pages on which the dynamic Component Presentation is used include a line of code that is be executed by the Content Distributor.

I'm guessing that "line of code" is RenderComponentPresentation() or an equivalent?

Do multimedia added with AddBinary or component Presentations with RenderComponentPresentations act the same in delivery? In other words, is the later also an implicit publish and are DCPs removed when no longer needed in delivery?

Background: I've seen questions related to link propagation (1, 2, 3, 4), but sometimes with phrases like "related items." I'm seeing the difference between the default resolving behavior, template logic that "publishes," but am not completely clear on delivery (yet). :-)

Update: On SDL Tridion 2011 SP1-1, I see:

• Queuing a page with an embedded component presentation where the component template is set to dynamic will also queue the DCP (visible in items to publish).
• A page with @@RenderComponentPresentation()@@ but no components won't show the referenced component in items to publish, but this DCP will show up in the broker database after a successful publish.

I understand that SDL Tridion will republish items that use an item you're publishing, which we might call "link propagation." We can change this behavior using Custom Resolvers or previously with the Event System.

AddBinary()

We can publish a multimedia component directly if it has a template associated with its schema. But we can also use AddBinary() to "implicitly" publish multimedia. Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it's removed.

RenderComponentPresentation()

Is this the same behavior, or even terminology, for RenderComponentPresentation()?

The docs explain (requires login):

If Pages include dynamic Component Presentations, dynamic Component Presentations are published. Pages on which the dynamic Component Presentation is used include a line of code that is be executed by the Content Distributor.

I'm guessing that "line of code" is RenderComponentPresentation() or an equivalent?

Do multimedia added with AddBinary or component Presentations with RenderComponentPresentations act the same in delivery? In other words, is the later also an implicit publish and are DCPs removed when no longer needed in delivery?

Background: I've seen questions related to link propagation (1, 2, 3, 4), but sometimes with phrases like "related items." I'm seeing the difference between the default resolving behavior, template logic that "publishes," but am not completely clear on delivery (yet). :-)

I understand that SDL Tridion will republish items that use an item you're publishing, which we might call "link propagation." We can change this behavior using Custom Resolvers or previously with the Event System.

AddBinary()

We can publish a multimedia component directly if it has a template associated with its schema. But we can also use AddBinary() to "implicitly" publish multimedia. Frank van Puffelen explains this isn't really publishing in the strict sense in the Binary Event Tracker post. When such a binary is no longer referenced in Content Delivery, it's removed.

RenderComponentPresentation()

Is this the same behavior, or even terminology, for RenderComponentPresentation()?

The docs explain (requires login):

If Pages include dynamic Component Presentations, dynamic Component Presentations are published. Pages on which the dynamic Component Presentation is used include a line of code that is be executed by the Content Distributor.

I'm guessing that "line of code" is RenderComponentPresentation() or an equivalent?

Do multimedia added with AddBinary or component Presentations with RenderComponentPresentations act the same in delivery? In other words, is the later also an implicit publish and are DCPs removed when no longer needed in delivery?

Background: I've seen questions related to link propagation (1, 2, 3, 4), but sometimes with phrases like "related items." I'm seeing the difference between the default resolving behavior, template logic that "publishes," but am not completely clear on delivery (yet). :-)

Update: On SDL Tridion 2011 SP1-1, I see:

• Queuing a page with an embedded component presentation where the component template is set to dynamic will also queue the DCP (visible in items to publish).
• A page with @@RenderComponentPresentation()@@ but no components won't show the referenced component in items to publish, but this DCP will show up in the broker database after a successful publish.