-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.X, 7.1.X, 7.2.X, Master
-
Fix Version/s: 7.0.0 DXP FP96, 7.0.10.15 DXP SP15, 7.0.X, 7.1.10 DXP FP20, 7.1.10.5 SP5, 7.1.X, 7.2.10 DXP FP9, 7.2.X, 7.3.X, 7.3.5 CE GA6, 7.3.10 DXP GA1, Master
-
Branch Version/s:7.2.x, 7.1.x, 7.0.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Git Pull Request:
Summary:
Web contents (with more than one version) expired and published from Web Content List, have more than one status in Live.
Steps to reproduce:
1.- Create basic web content "wc1" in staging (1.0 version).
2.- Publish to Live from the web content directly, in the web content list.
"wc1" (1.0 version) is showed in Live in the web content list.
3.- Modify "wc1" (e.g. Title or similar) (1.1 version).
4.- Publish to Live from the web content directly, in the web content list.
"wc1" (1.1 version) is showed in Live in the web content list.
5.- Expire "wc1" from the web content directly, in the web content list.
In Staging, the status of "wc1" is Expired.
6.- Publish to Live from the web content directly, in the web content list.
Result expected: "wc1" is showed in Live, in the web content list, with the status Expired (only one status).
Result obtained: "wc1" is showed in Live, in the web content list, with the status Approved and the status Expired.
- causes
-
LPS-123875 Latest published version of a web content article is not displayed
- Verified
- is caused by
-
LPS-120527 Expire web content in Staging isn't consistent with Live
- Closed