Problem/Motivation

When adding a time for a notification to be sent out, no timezone is mentioned and the display of time is inconsistent.

Steps to reproduce

- Add a content notification to a piece of content and enter 5:00:00 PM as the time of the notification (for a future date). Note that there is no indication of a time zone. I am in Mountain Time (during Daylight savings), so I am entering 5:00:00 PM expecting Mountain Time.
Content notification added for 5 pm local time (which is mountain time).

- Go to the content notification view and look at the row for the new content notification. (admin/structure/content_reminder). Note that the format of the time is different than how the time was entered when creating the notification. Also note that the format is in GMT and appears to be created expecting that the time is in the eastern time zone (during daylight savings). 5PM mountain time (during daylight savings) should be represented as 23:00:00 GMT. Instead, 21:00:00 GMT indicates that 5PM Eastern time (during daylight savings) was entered.
content notification indicates time in GMT and it does not correlate to mountain time zone.

Proposed resolution

Uncertain, but one option would be to do the following:
- provide a configuration for the time zone to be used when creating a notification.
- display the expected timezone on the notification form (i.e. 'all times should be Eastern')
- on the overview page, modify time format to be consistent with the time entered in the notification.
- always default to Eastern maybe?

Comments

timozura created an issue. See original summary.

timozura’s picture

Version: 1.0.0 » 2.0.0-beta3
Status: Active » Fixed

This was fixed as part of https://www.drupal.org/project/content_reminders/issues/3559713.

The date and time on the collections table has been formatted for consistency with the date and time on the content reminder.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.