-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.1.X
-
Fix Version/s: 7.1.10 DXP FP13, 7.1.X
-
Component/s: ~[Archived] WCM > Navigation
-
Branch Version/s:7.1.x
-
Backported to Branch:Committed
-
Fix Priority:5
-
Git Pull Request:
Steps to Reproduce:
- Create a Page Fragment and add the following in the HTML section:
<lfr-widget-nav> </lfr-widget-nav>
Example:
<div class="fragment_33778"> <lfr-widget-nav> </lfr-widget-nav> </div>
- Create a Private Widget Page
- Create a new public content page and add the fragment
- Edit the public content page and check the default content of the portlet
Expected Result: Since the page is public it should show the primary navigation
Actual Result: Private Pages Hierarchy is shown.
Branch: Reproduced. 7776e9ad1c3b14b51608628037e5689b2ff92032
DXP-1 to DXP-11 Reproduced.
Master: Not reproduced
- is related to
-
LPS-82713 Wrong default configuration for Navigation Menu widgets in a fragment
- Closed
-
LPS-89154 Allow the edition of a page template and display page through an edit mode instead of through the control panel
-
- Closed
-
- Testing discovered
-
LPS-97451 Fragment with navigation menu not taking into account the configuration in edit mode
- Verified