Setup
...
How To
MaxPublishDepth
4 min
the \<maxpublishdepth> option controls the maximum depth at which folders can remain published this feature was implemented for a customer who has folders further down the tree which have sensitive names (e g terminated employees) and shouldn't be published to the general public they determined that minimum level that folders with sensitive names were like to exist at and set the \<maxpublishdepth>to lower than that minimum notes please note that this option does not apply to folders that have child folders that are secured; parents of secured folders will always remain published a folder that previously had a depth greater than the \<maxpublishdepth>is not automatically republished if the \<maxpublishdepth>is reduced steps in activate administrator navigate to resources/folders configure \<maxpublishdepth> parameter on a folder share rescan folder share by right clicking on the folder share and selecting "synchronise file system" from the "folderresource tasks" menu folders within that share that do not have secured children and who's depth is greater than the \<maxpublishdepth>will be unpublished further notes and examples folders are unpublished based on rules when \<maxpublishdepth> is changed from 0 to 1 folders are not unpublished when \<maxpublishdepth> is changed without a resync of the file system the \<maxpublishdepth> parameter does not need to be set at the root of "folders" examples in the below sample folder structures, black folder names are published, grey folders are unpublished the name of the folder indicates it's specific security type \<maxpublishdepth> at the root is set to 2 maxpublishdepth = 0 maxpublishdepth = 3 below folders of depth greater than 3 are unpublished, unless they have secured folders under them