Date format has changed for fields in newer versions of dotCMS

[erickgonzalez]

Parent Issue

#25008

Problem Statement

Same as the issue above, seems that we only fixed for API responses but no for VTL ones.

Steps to Reproduce

1- Create a widget with the following code:

PostingDate vs ModDate</br>
#foreach($con in $dotcontent.pull("+contentType:Blog +(conhost:48190c8c-42c4-46af-8d1a-0cd5db894797 conhost:SYSTEM_HOST)",10,"modDate desc"))
$con.postingDate vs. $con.modDate <br>
#end

2- Add the widget to a page
3- Check the dates, are diff formats

Acceptance Criteria

The date format should be the same as the one of the modDate.

dotCMS Version

23.01 +

Proposed Objective

Customer Support

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.zendesk.com/agent/tickets/112060

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[wezell]

the above compares the .toString() methods of the Date objects. The db date is a java.sql.Timestamp and the contentType date is a java.util.Date - this is not really an issue as the values are not wrong? @erickgonzalez can you verify?

#foreach($con in $dotcontent.pull("+contentType:Blog",10,"modDate desc"))
$con.postingDate vs. $con.modDate
$con.postingDate.class vs. $con.modDate.class <br>
#end

Fri Jul 12 18:15:00 UTC 2019 vs. 2023-06-21 14:24:48.777
class java.util.Date vs. class java.sql.Timestamp 

[dsolistorres]

PR ready for this issue:
#25521

[josemejias11]

Approved QA - Tested on master_dc3cb0b_SNAPSHOT // Docker // macOS 13.0 // FF v113.0

[erickgonzalez]

Not reproducible in 22.03 LTS