Timeline for Is RenderComponentPresentation() like AddBinary()?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2013 at 13:12 | vote | accept | Alvin Reyes | ||
| Sep 12, 2013 at 8:18 | history | edited | Bart Koopman | CC BY-SA 3.0 |
updated answer based on comment
|
| Sep 12, 2013 at 8:12 | comment | added | Bart Koopman |
I've tested it out with a footer DCP which I have a RenderComponentPresentation() call for in the Page Template, but it's not actually on the Page. As expected when viewing the items to publish, (result of the resolve action) it is not listed in there. But what I didn't expect was that after publishing that Page, my DCP was indeed published, so I adjusted my answer. And indeed as Will answered, when you unpublish the Page, the Template code is not executed, so that DCP will NOT be unpublished.
|
|
| Sep 11, 2013 at 16:53 | comment | added | Alvin Reyes |
I see your first part--queuing a page with DCPs in it will show the DCPs in the Items to Publish list (with no rendering done yet, right?). But I seem to be able to actually "publish" a DCP not referenced on another page with no components and RenderComponentPresentation() in its DWT TBB. It ends up in storage (broker database), though Show Items to Publish won't show it when queued for publishing. Will Price describes this "RenderCP = publish" behavior in this answer, but maybe there's a difference with in-page DCPs and the API call?
|
|
| Sep 11, 2013 at 9:02 | history | answered | Bart Koopman | CC BY-SA 3.0 |