-
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.10.5 SP5, 7.1.X, 7.2.10 DXP FP6, 7.2.X, 7.3.3 CE GA4, 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:
Reproducing Steps
- In a given site, create a new web content.
- Mark the web content as expired.
- Check the expiration timestamp in the edit view under Schedule > Expiration Date.
- Export the site.
- Create a new site.
- Import the original site with the default options.
- Check the expiration timestamp for the imported content.
Observed: The expiration timestamp is the same as the original's.
- Repeat the import process in the new site with the same default options.
- 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.)
- is duplicated by
-
LPS-114592 Expiration date is not maintained the second time a web content is imported
- Closed