Timeline for Get "local" Page using Core Service based on Component
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2016 at 15:15 | comment | added | Chris Morgan | This is my preferred solution, as much more efficient. There are a couple of gotchas to be aware of 1. Only already published pages appear when triggering the publish from a Component 2. You might want IncludeComponentLinks set to true, so that Component Links flag indirect page links | |
| Sep 1, 2016 at 15:14 | vote | accept | Chris Morgan | ||
| Aug 31, 2016 at 15:00 | comment | added | Chris Morgan | Yea. I just tried that. I think with a Component that makes no difference. More testing required and I'll report back | |
| Aug 31, 2016 at 14:58 | comment | added | Dave Forber |
I think you can control that with ResolvePurpose.Publish vs ResolvePurpose.RePublish, though I confess I've not tested that ... just making the assumption :)
|
|
| Aug 31, 2016 at 14:55 | comment | added | Chris Morgan | Thanks @Dave. This is an interesting solution, and certainly improves code cleanliness and performance. Only issue is I don't think it will include pages that have not previously been published. I think by publishing the Component I will only get pages previously published in the resolved items. I could be wrong though | |
| Aug 31, 2016 at 14:36 | history | answered | Dave Forber | CC BY-SA 3.0 |