The submitted patch mitigates the problem as much as possible, but has
some limitations due to the way Mahra stores dates/times in the DB.

A full fix will require changing Mahara to store dates/times as a unix
epoch value.

You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask 
on #mahara-dev or forum before editing or unsubscribing it!

  Times reported inaccurately when DB timezone does not match PHP

Status in Mahara:
  In Progress

Bug description:
  for a full breakdown of the problem.

  TL,DR Mahara has no support for multiple timezones and assumes that
  the PHP date.timezone and the database server's timezone are
  identical. If they are not, then all dates that get stored into the
  database and displayed back to the user will be off by (Database UTC
  offset - PHP UTC offset).

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to