Bug 204107 - Web site navigation tree is not evaluated as a tree.
Web site navigation tree is not evaluated as a tree.
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Devel
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McCune
Red Hat Satellite QA List
Depends On:
Blocks: 145467
  Show dependency treegraph
Reported: 2006-08-25 12:49 EDT by Ken Ganong
Modified: 2008-10-14 16:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-14 16:27:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Navigation, Active nodes error. (265.48 KB, image/png)
2006-08-25 12:49 EDT, Ken Ganong
no flags Details

  None (edit)
Description Ken Ganong 2006-08-25 12:49:26 EDT
Created attachment 134934 [details]
Navigation, Active nodes error.
Comment 1 Ken Ganong 2006-08-25 12:49:26 EDT
When finding the navigation node to activate for a given url, our navigation
system does not evaluate as a tree of nav nodes.  Instead it evaluates the best
node by checking against a map of nav nodes whose keys are urls.

So,  what if we had a piece of navigation that has an acl preventing the user
from seeing that nav node.  If the nav nodes were evaluated as a tree, than all
of the nodes under that nav node would "inherit" the acl because that entire
section of the tree wouldn't be viewable.  Instead, if a user enters a url that
corresponds to a nav-node under the acled node, they would see an activated node
for the url that they typed, but it would not show the parent node.

The work-around is to add the parent's acl to every child node.

See the screenshot.
Comment 2 Amanda Carter 2008-10-14 16:27:34 EDT
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.

Note You need to log in before you can comment on or make changes to this bug.