U4-5324 - Users with a content root node, cant have custom tree roots

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.

Comments

Shannon Deminick 23 Sep 2014, 05:08:32

This fix caused this issue: U4-5460


Priority: Normal

Type: Bug

State: Fixed

Assignee: Per Ploug

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version: 7.1.5

Sprint:

Story Points:

Cycle: