Dynamic root cannot start at root content? #15704
james-whittington1
started this conversation in
Features and ideas
Replies: 1 comment 4 replies
-
Sounds like a okay idea, but for the specific use case, what are the problems with choosing the settings node by key? The key id not the Id, so it will be the same on all environments. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a site where a settings node is outside of the site root, and there is no way to select it using the new dynamic root except picking it by key.
As an interim solution I have built a query step that gets the pages at root, but it seems like this is an origin, as it step it just discards whatever else precedes it.
An origin of "Root content" which returns the same as _contentService.GetRootContent() would be a reasonably useful kind for websites that have multiple root content nodes I think?
Beta Was this translation helpful? Give feedback.
All reactions