-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE, Master
-
Fix Version/s: 7.0.0 DXP FP58, 7.0.0 DXP SP9, 7.0.X, 7.1.X, Master
-
Branch Version/s:7.0.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Git Pull Request:
1. Create a new blank site 's1'.
2. Add a public page to it.
3. Create two web contents
4. On the page created at step 2, place an asset publisher and a web content display portlet.
5. The asset publisher lists wc1 and wc2. In the WCD portlet, select wc1 and save.
6. Turn on local staging for site S1, uncheck Web Content.
7. Go to that page. Live view shows the asset publisher with wc1 and wc2 and the WCD portlet shows, as expected, wc1.
8. Now switch to the Staging view.
Result: wc1 is showed in the WCD portlet and is shown in the asset publisher, but wc2 is not shown in the asset publisher.
Expected: asset publisher should list both wc1 and wc2
- is related to
-
LPE-15594 When web content is unstaged, asset publisher looks for them in the wrong scope
-
- Open
-
-
LPS-69069 During enabling staging with web content unckecked, journal article database records are created for the staging site
- Closed
- relates
-
LPS-84204 Having a staged site with web content is unstaged, missing references to a JournalArticle to that site doesn't work fine
- Closed
- Testing discovered
-
LPS-70072 NPE through out after enabling local staging without web content
- Closed