-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.X EE, 6.2.X EE, 7.0.0 M3
-
Fix Version/s: 6.1.X EE, 6.2.2 CE GA3 , 6.2.X EE, 7.0.0 M2
-
Component/s: Web Content > Web Content Administration
-
Branch Version/s:6.2.x, 6.1.x
-
Backported to Branch:Committed
-
Story Points:8
-
Fix Priority:4
-
Git Pull Request:
The scheduled task to "approve" scheduled web content is changing the modified date and this opperation is not changing the content.
This task should be change only the statusDate, indicating the date in where the status was changed.
Steps to reproduce:
1. Set journal.article.check.interval=2 in the portal-ext.properties and restart the server.
2. Create a Web Content:
WC1: Title=WC1, Content=WC1 and in the Scheduled dates set the display date as the current date plus 2 minutes.
3. Launch the next query:
SELECT urlTitle,createDate,modifiedDate,displayDate,status,statusDate FROM JournalArticle;
urlTitle createDate modifiedDate displayDate status statusDate wc1 2014-09-02 18:19:25.0 2014-09-02 18:19:25.0 2014-09-02 18:20:00.0 7 2014-09-02 18:19:25.0
Note that the status=7 and the createDate, modifiedDate, displayDate and the statusDate are 2014-09-02 18:19:25.0
4. Wait for 2 minutes and launch again the same query
urlTitle createDate modifiedDate displayDate status statusDate wc1 2014-09-02 18:19:25.0 2014-09-02 18:20:59.0 2014-09-02 18:20:00.0 0 2014-09-02 18:20:59.0
Result the status=0 and the modifiedDate and the statusDate are equals, just 2014-09-02 18:19:25.0.
Expected the modifiedDate is not changed and only it is updated the statusDate.
Reason an status change should not update the metadata of a Web Content, specially if this metadata are used in the wcm interface.
This is a regression of behaviour after introduce the SCHEDULED status in WC.
NOTE: A similar issue happens if you send a WC to the Recycle bin and then restore it.