| Summary: | Invisible navigation node still shown in Sitemap portlet | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Martin Weiler <mweiler> |
| Component: | Portal | Assignee: | Martin Weiler <mweiler> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0.GA, 5.1.1.GA | CC: | epp-bugs, mweiler |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0.ER01 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-1150 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-06 12:47:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Martin Weiler
2011-09-06 11:53:55 UTC
Workaround Description: Removed: For EPP 5.1.x, edit gatein.ear/02portal.war/groovy/webui/core/UISitemapTree.gtmpl and add the following:
@@ -28,6 +28,10 @@
size++;
node = treeNode.getNode();
+
+ // continue if node is invisible
+ if(!node.isDisplay()) continue;
+
nav = treeNode.getNavigation();
Added: For EPP 5.1.x, edit gatein.ear/02portal.war/groovy/webui/core/UISitemapTree.gtmpl and add the following:
{code}
@@ -28,6 +28,10 @@
size++;
node = treeNode.getNode();
+
+ // continue if node is invisible
+ if(!node.isDisplay()) continue;
+
nav = treeNode.getNavigation();
{code}
Fixed in GateIn trunk / EPP 5.2 branch by https://source.jboss.org/changelog/GateIn?cs=6783 Release Notes Docs Status: Added: Not Required Release Notes Docs Status: Removed: Not Required Added: Not Yet Documented Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue. |