We have moved to GitHub Issues
Created by Claus Jensen 05 Feb 2017, 09:24:25 Updated by Sebastiaan Janssen 04 Sep 2017, 09:33:03Tags: Backport
If you need to hook into the
.Save event of the content service and trigger a send to publication - you will end up in an endless loop due to the
.SendToPublication method calling
.Save again, while not allowing to set
raiseEvents to false.
Shouldn't this be the other way around? SendToPublication's only real job is to raise events. In theory it shouldn't actually Save the item it unnecessary, or an overload could have a bool to Save or not to save, but seems odd to have an overload to disable emitting events since that is literally the sole responsibility of this method.
Hmm you're right. Just looked at it again and yep - it wouldn't make sense to not trigger those events. I'll change it to being able to cancel out the
Assignee: Claus Jensen
Backwards Compatible: True
Affected versions: 7.5.8
Due in version: