Timezone Issue in Media Gallery

Has this been customized in any way?  The APIs will always return data in the accessing users timezone unless you potentially have widget code double adjusting.

No, it has not been adjusted at all.  It appears to be returning the same timestamp from the database, but with an EST timezone offset attached.

For instance, in the DB I have: 
2019-07-09 13:01:52.370

When I get the date from the media object it has the exact same date/time that is in the DB, but it also has a -04:00 offset which I believe is EST - Like the system is attaching a timezone but not altering the time of the date.

I'm on version 9.0 and pushing it through this method gave me the correct time.

            public DateTime ToUserTimezone(DateTime date, Telligent.Evolution.Extensibility.Api.Entities.Version1.User user)
            {
                var newDate = DateTime.SpecifyKind(date, DateTimeKind.Utc);
                return TimeZoneInfo.ConvertTime(newDate, TimeZoneInfo.FromSerializedString(user.TimeZoneInfo));
            }

No, it has not been adjusted at all.  It appears to be returning the same timestamp from the database, but with an EST timezone offset attached.

For instance, in the DB I have: 
2019-07-09 13:01:52.370

When I get the date from the media object it has the exact same date/time that is in the DB, but it also has a -04:00 offset which I believe is EST - Like the system is attaching a timezone but not altering the time of the date.

I'm on version 9.0 and pushing it through this method gave me the correct time.

            public DateTime ToUserTimezone(DateTime date, Telligent.Evolution.Extensibility.Api.Entities.Version1.User user)
            {
                var newDate = DateTime.SpecifyKind(date, DateTimeKind.Utc);
                return TimeZoneInfo.ConvertTime(newDate, TimeZoneInfo.FromSerializedString(user.TimeZoneInfo));
            }

What version are you on?

9.0.0.49692

Nevermind, I see what you said.  IT is possible to have these types of issues in 9.  Have you looked at 10 and seen the same behavior?  10.0 Overhauled the entire datetime infrastructure. Unfortunately 9.X went end of life last month and has not been receiving updates in some time.

Note in 10 you cannot use that method, it should be unnecessary and could cause other issues

Thanks Patrick.  We'll use it internally for now as we have a business requirement where users need to upload certain PDFs by a deadline and our admins need to know if they met the requirement for issuing CEU credits...I'll note it and remove that call when we upgrade.