U4-2834 - Umbraco version (6.1.5) createDate looses offset on save and publish after application restart

Created by Thomas Skyldahl Sørensen 10 Sep 2013, 20:40:25 Updated by Shannon Deminick 21 Jun 2017, 07:58:15

I have been trying out indexing umbraco content using ElasticSearch and noticed a difference in createDate format in the json delivered to ElasticSearch after restarting the applicaction.

Before restart the createDate contains offset information but after a application restart it looses the offset and is considered to be in UTC or Zulu time but the time component doesn't reflect the offset.

eg.

2013-09-10T22:05:46.3835707+02:00

becomes

2013-09-10T22:05:46Z

this only happens after restarting the application.

I am using the ContentService to listen to the events fired after save and publish and I am using the new IContent in the EventArgs to extract the information for my json.

I think this could be a issue in countries where the difference in offset is greater than my example.

Comments

Sebastiaan Janssen 11 Sep 2013, 06:31:57

@Morten could this be a difference in the way the datetime is queried and returned to the ContentService first and then cached in memory differently?


Shannon Deminick 21 Jun 2017, 07:58:15

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Normal

Type: Bug

State: Closed

Assignee: Morten Christensen

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.1.5

Due in version:

Sprint:

Story Points:

Cycle: