Affects Version/s: 6.2.X EE, 7.0.X, Master
Component/s: Web Content > Web Content Administration
Steps to reproduce:
1. Add a new web content on Staging site without expirationDate. And then place one asset publish portlet in one page of staging site.
2. Publish the web content to Live site without checking version history.
Check: The expirationDate of record on both staging and live should be 'null'.
3. Edit the web content on Staging site with a new expirationDate.
4. Publish the web content to Live site without checking version history.
Check database: All versions of web contents on staging have the same expirationDate. However, only the latest version of web content on live site has the expirationDate. The expirationDate of previous 1.0 version is 'null'
Current Result: After passed the expirationDate, all versions on staging site are expired. However, only the latest version on live site are expired. The previous old versions are still in 'Approved' status. Check the asset publish portlet in live site, the 1.0 approved version will display.
Expected Result: All versions of web content on live site should expired automatically.