Expiration date is not maintained the second time a web content is imported

• 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 FP93, 7.0.10.14 DXP SP14, 7.0.X, 7.1.10 DXP FP18, 7.1.X, 7.2.10 DXP FP6, 7.2.X, 7.3.3 CE GA4, Master
• Component/s: Staging > Export/Import, Web Content > Web Content Administration
• Labels:
  • ee-ts
  • liferay-fixpack-de-93-7010
  • liferay-fixpack-dxp-18-7110
  • liferay-fixpack-dxp-6-7210
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/liferay-echo/liferay-portal/pull/840

Reproducing Steps

1. In a given site, create a new web content.
2. Mark the web content as expired.
3. Check the expiration timestamp in the edit view under Schedule > Expiration Date.
4. Export the site.
5. Create a new site.
6. Import the original site with the default options.
7. Check the expiration timestamp for the imported content.
   Observed: The expiration timestamp is the same as the original's.
8. Repeat the import process in the new site with the same default options.
9. Check again the expiration timestamp for the imported content.
   Expected: The expiration timestamp is the same as the original's.
   Observed: The expiration timestamp is (very close to) the current timestamp. (It's the timestamp at the moment of import.)