We have moved to GitHub Issues
Created by Per Ploug 08 Aug 2014, 08:53:50 Updated by Shannon Deminick 23 Sep 2014, 05:08:32
A user with a content root node set on the user profile cannot have a custom root node set on content picker dialogs.
For instance, user A has his content tree root set to = "news" - but a content picker dialog is set to use the path "$site/newsarea/section" - even if the user has access to this path - it will not be set since dialog trees will only get a custom root if the user has access to the entire content tree.
So the user will get a dialog back, which uses "news" as the content root - instead of the expect the section as root.
This fix caused this issue: U4-5460
Assignee: Per Ploug
Backwards Compatible: True
Due in version: 7.1.5