First off, now this feature is extracted into a designated getItemReferences pipeline, ready for extension.
Secondly, out of the box, the list of references is extended. Now referring aliases and all content and media references of the currently processed publishing candidates are being added to the publish queue:
<processor type="Sitecore.Publishing.Pipelines.GetItemReferences.AddItemCloneReferences, Sitecore.Kernel"/>
<processor type="Sitecore.Publishing.Pipelines.GetItemReferences.AddFileDropAreaMediaReferences, Sitecore.Kernel"/>
<!-- NEW -->
<processor type="Sitecore.Publishing.Pipelines.GetItemReferences.AddItemLinkReferences, Sitecore.Kernel"/>
<processor type="Sitecore.Publishing.Pipelines.GetItemReferences.AddItemAliasReferences, Sitecore.Kernel"/>
This obviously means that the number of items added to the queue will increase dramatically, something to be aware of.
This feature is designed to be used only in Single Item publish mode, which will also work when you publish from workflow or Page Editor, the use case when it is very important to pull in all items the currently published item is referencing in order for a particular page to be fully published.
Finally, we are planning some further optimization of this process, which will result in fewer items being added as references during publishing. Hopefully in Update-1 for 7.2.
Good day now.
Hi Sitecore 7.2 Dev Team, Great post, Do you know which is the depth that Related Items take? or maybe you know if there a possibility to limit the depth in related items, this in order to avoid potentially publishing ALL site items that are related?. Thanks in advanced.
It is being reported that there is a bug with the "publish related" that causes things to be published 3 times. Is this true?
Hi Jim, I believe it is a known issue now, yes. An upcoming update should have the fix for it. I'd ask support team for the reference id. -alex
7.2 Update 3 fixed the issue. sdn.sitecore.net/.../Release History SC72.aspx
How does this impact a WFFM form item that is referenced on an item which is published through the auto publish workflow action with the related parameter set to 1? Should the form item be published as well? I'm not seeing this happen in reality.
Has there been any improvements to this in Sitecore 9.0, as we are trying to use the related Items publish on a node with Subitems selected, and it has been processing for past 3 days.