Old version of web content are not expired when publishing without version history

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.X EE, 7.0.X, Master
• Fix Version/s: 6.2.X EE, 7.0.0 DXP FP33, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, 7.1.0 M1, 7.1.X, Master
• Component/s: Web Content > Web Content Administration
• Labels:
  • ee-ts
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-33-7010
  • liferay-fixpack-portal-164-6210
  • liferay-fixpack-portal-168-6210
• Branch Version/s:
  7.0.x, 6.2.x
• Backported to Branch:
  Committed
• Git Pull Request: https://github.com/hhuijser/com-liferay-journal/pull/16

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.