I'm interested in which mechanism is used when
Also Publish/Unpublish in Child Publications option is checked. To me it's logical that this is performed by the
Resolver. Besides common logic, another telltale is that via code we can set this option in the
If that is indeed the case, I'm interested whether it's possible to customize its functioning similar to building a Custom Resolver for manipulating resolved items, but for omitting some "resolved" Publications?
In Web 8 this can easily be done OOTB, however this question is for 2013 SP1.
I see that mentioning Web 8 has only caused confusion. What I meant is that in Web 8 I simply do not add a BPT to the relevant Publications and no transactions will be created for them in the queue. I want to achieve the same but in 2013 SP1.
In other words, I want an option to remove entire Publications from the set of "resolved publications" which a (un)publishing action with the
Also Publish/Unpublish in Child Publications creates. So not a custom resolver for items in the Publications, but entire Publications themselves. Hope that makes sense.
Replied here because the comment section has limited capability...
Yes, I am familiar with the concept of publication targets/target types, but such an approach would remove the capability of editors to publish from those publications altogether. Those publications are for example "content publications" or "pages publications" and they need to have the option to publish in all children so that with a single publish, the item is published in all the "site publications". Only the "site publications" are relevant for publishing from the websites' perspective.
One approach is to use a custom resolver and empty out all the transactions from the 'irrelevant' publications, but that way there are many (essentially) empty transactions created, just to be emptied in the very next step. This makes some unnecessary load on the DB and the system, clogs up the publishing queue making it impossible to use (we have publishing of (tens of) thousands of items on a daily basis), interferes with our reporting on publishing speed, etc.
What would be better is to have the option to influence the "list of resolved publications" themselves which are "calculated" based on the Blueprinting when the
Also Publish/Unpublish in Child Publications is checked. So instead of working on publish transactions of irrelevant publications, my idea is to remove them somehow before they even appear. A "pre-resolver" for the irrelevant publications, but on the publication scale if you will.
In other words, I want to tap in the
Also Publish/Unpublish in Child Publications and modify it's behavior. Is that possible?