From 18047a7cfbae21ad618e9c9933601e54dc3768e7 Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Mon, 17 Feb 2025 12:45:51 +0100 Subject: [PATCH] Only filter post retrieval of entities for start nodes if working with entities that support start nodes. (#18287) --- src/Umbraco.Web.BackOffice/Controllers/EntityController.cs | 1 + 1 file changed, 1 insertion(+) diff --git a/src/Umbraco.Web.BackOffice/Controllers/EntityController.cs b/src/Umbraco.Web.BackOffice/Controllers/EntityController.cs index c54344a239..f4ef16e041 100644 --- a/src/Umbraco.Web.BackOffice/Controllers/EntityController.cs +++ b/src/Umbraco.Web.BackOffice/Controllers/EntityController.cs @@ -895,6 +895,7 @@ public class EntityController : UmbracoAuthorizedJsonController // Filtering out child nodes after getting a paged result is an active choice here, even though the pagination might get off. // This has been the case with this functionality in Umbraco for a long time. .Where(entity => ignoreUserStartNodes || + (objectType == UmbracoObjectTypes.Document || objectType == UmbracoObjectTypes.Media) is false || (ContentPermissions.IsInBranchOfStartNode(entity.Path, startNodeIds, startNodePaths, out var hasPathAccess) && hasPathAccess)) .Select(source =>