[Steven Zahm]

@ Len

The database is fine, I believe this issue is related to a timezone issue as I can not replicate it. I’m certain this issue popped up because the dates can now be properly internationalized.

Another user resolved the issue by manually setting the timezone with this function: date_default_timezone_set

They’ve kindly given me access to the server and site so I can debug this.

As for putting the date in as 9999 … the upcoming list calculates the next date, not the actual date. For example lets say a persons birthday occurs in April, since it is now June, the birthday will show up as the date in April 2014. Conversely, if the person’s birthday is in July, it will show up with a 2013 date in July.