Hi, The date is indeed stored in ISO format. However, on an author running in UTC making changes from a machine running in a different timezone (I picked randomly, GST which is UTC+4), the Date component shows local time, but stores it as the UTC time, so my content would be activated 4 hours late.
I shall raise an issue in jira and hopefully add a patch. (Currently on 4.2.2, CE) Toby. On 9 Feb 2011, at 13:59, Jan Haderka wrote: > > AFAIK all of the node data of type Date store time in ISO format. So the > conversion should be transparent and activation should happen at correct > time. If not please open issue in jira. > > HTH, > Jan > > On Feb 9, 2011, at 11:53 AM, Toby O'Rourke wrote: > >> >> Hi, >> >> I can't find any documentation that clearly explains how Magnolia handles >> time. Specifically, if my server is running in UTC but my site is aimed at a >> different locale, with a different time zone (for example EST) if an editor >> schedules content for activation at 09:00, will that be 09:00 UTC or 09:00 >> EST? How can I make it take account of different timezones while running the >> server in UTC? >> >> Thanks, >> >> Toby. >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
