this functionality does not work for derived catalogs and catalogs owned by template sites. The intent
of this was to also include all super catalogs in the query but this only works for standard sites and catalogs
within a standard site. Rather than using this mode, just ensure that you are not in MultiTenantStateManager.isExplicitCatalogFilterMode()
and the existing CatalogFilterEnabler will do the right thing.
this can be expensive depending on the member size. Consider a query approach instead. Review MultiTenantSiteUtil
helper methods that may be applicable.
This implementation performs poorly for large quantity catalog assignments. Callers should be
refactored to ascertain catalog assignment information differently, likely through a more direct query oriented solution.
this functionality does not work for derived catalogs and catalogs owned by template sites. The intent
of this was to also include all super catalogs in the query but this only works for standard sites and catalogs
within a standard site. Rather than using this mode, just ensure that you are not in MultiTenantStateManager.isExplicitCatalogFilterMode()
and the existing CatalogFilterEnabler will do the right thing.
this can be expensive depending on the member size. Consider a query approach instead. Review MultiTenantSiteUtil
helper methods that may be applicable.
this functionality does not work for derived catalogs and catalogs owned by template sites. The intent
of this was to also include all super catalogs in the query but this only works for standard sites and catalogs
within a standard site. Rather than using this mode, just ensure that you are not in MultiTenantStateManager.isExplicitCatalogFilterMode()
and the existing CatalogFilterEnabler will do the right thing.