Hi Scott,
In theory whether there is a timezone issue or not the notifications should go in the end. In theory there may be an inaccurancy relating to DST, but shouldn't really be any more than that. The module checks over the previous 30 days (which is far larger than any DST error!!), for notifications to send, so should pick up any ion that period. So things to check:-
- Are you sure someone has registered for a notification for the event on the detail page.
- Have you checked the event log, it records any messages being sent
DotNetNuke.Modules.Events.EventNotification, DotNetNuke.Modules.Events
Event Notification completed. 1 Notification(s) sent!
- You can try running the SQL below, in the Host/SQL box. Don't tick 'Run as script'. If you don't get any rows back, there are no notifications to send. If you do, get rows back and the n.NotifyByDateTime is in the past then we have a problem
SELECT n.NotificationID, n.EventID, n.PortalAliasID, n.UserEmail,
n.NotificationSent, n.NotifyByDateTime, n.EventTimeBegin, n.NotifyLanguage,
e.TimezoneOffset, n.ModuleID
FROM {databaseOwner}[{objectQualifier}EventsNotification] as n INNER JOIN
{databaseOwner}[{objectQualifier}Events] as e ON n.EventID = e.EventID AND n.NotifyByDateTime <= DATEADD(minute, e.TimezoneOffset,
getutcdate())
WHERE (n.NotificationSent = 0)
ORDER BY n.NotifyByDateTime
Hope this helps
Roger