In addition to this old question: SetPublishedTo with CoreService
I have another question for the new Tridion 2011 EventSystem
I'm updating our EventSystem from the old TOM API to CoreServices... which's impact on re-work I greatly underestimated :))
With CoreService it is no longer possible to fake-publish a page, i.e. Page.SetPublishedTo();
This is something we used so content managers could:
- create component (ES automatically creates page, publishes to staging website, and set IsPublishedTo(live) property)
- check on staging website
- publish component to live website - component is publishable to live because we set Page.SetPublishedTo()
With CoreServices that "tweak/hack" is no longer available, meaning that our content managers won't be able to publish their components to live anymore. In stead they have to find the page that has the component on it and publish that.
Is there a viable work-around to save our servicedesk from countless of calls about 'components not publishing to live!' ?
- get pages containing this component
- if page is not yet published to target, then publish page to that target in stead of component
Or is this a wrong thought?
Or is it easier and still future proof to just use the older TOM.Net API for this?
Tnx for helping me out, Robin