Enable or disable publishing deep scan
|
Applies to |
Content Management |
|---|
When you publish a single item you can choose to publish related items at the same time. You must choose to publish related items for the deep scan feature to take effect.
Examples of related items include:
-
Clones – items that are clones of the selected item.
-
Media items – media items that are referenced by the selected item.
-
Content items - data sources that are referenced by the selected item.
-
Design items - renderings, layouts and templates used by the selected item.
-
Aliases – items that are aliases of the selected item.
The deep scan feature affects related items only. It does not apply to sub-items, or sub-items of related items.
If, when publishing an item, the user does not explicitly specify to also publish related items, then the deep scan feature does not come into play.
The publishing process uses the Link database to look up references from the item being published. The deep scan setting determines if related items are published recursively, that is, whether to publish related items of related items)
-
If deep scan is enabled, related items are published recursively - that is, related items of related items are also published. Deep scan is enabled by default.
-
If deep scan is disabled, only directly related items are published.
You can disable deep scan to reduce the number of publishing operations and improve performance.
Disable deep scan
To disable deep scan in Sitecore 9.1 and earlier, patch the /App_Config/Sitecore.config configuration file by adding a <DeepScan> element with a false value to the AddItemLinkReferences pipeline as shown:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<sitecore>
<pipelines>
<getItemReferences>
<processor type="Sitecore.Publishing.Pipelines.GetItemReferences.AddItemLinkReferences, Sitecore.Kernel">
<DeepScan>false</DeepScan>
</processor>
</getItemReferences>
</pipelines>
</sitecore>
</configuration>