For instance, if I go to Schedule Component interface, the Evaluation Date default is:

2011-09-24 08:02:38
The date in GMT. Format: 2011-09-25 08:02:38 or other values in GMT known by the PHP strtotime() function like "+1 day". Relative dates like "+1 day" or "now" relate to the evaluation time.

So to get a component to trigger at midnight, I set a rule to trigger at `16:00`

However having set this, the rule has just triggered now at 16:00 HKT (+0800), and the current GMT time is 08:00 GMT.

The hosts time date is set to:

Sat Sep 24 16:01:58 HKT 2011

And the Drupal Region Settings Default Time Zone is set to: Asia/HongKong +0800

Comments

carn1x’s picture

carn1x commented
Component: User interface » Scheduler
Priority: Normal » Major
carn1x’s picture

carn1x commented
Priority: Major » Normal

Actually back to normal, the 'workaround' is simple enough.

shaundychko’s picture

shaundychko
Location Vancouver, Canada
commented

and what is the workaround, exactly?

carn1x’s picture

carn1x commented

Oh sorry, I should clarify, the workaround for me was to simply ignore that the scheduler was prompting for GMT, and just input the time as the local time according to the server.

shaundychko’s picture

shaundychko
Location Vancouver, Canada
commented

Yes, I can confirm that ignoring the prompt for GMT is fine. Maybe this text is out of date. I'm using the latest 6.x version, by the way.

star-szr’s picture

star-szr
he/him
Primary language English
commented
Title: Scheduled Component interface instructs to use GMT, however component is triggering at local time » Rules interface instructs to use GMT, but evaluation is against local time
Version: 7.x-2.0-rc2 » 7.x-2.x-dev
Component: Scheduler » Documentation

The issue here is beyond just the Scheduler component, it applies to all dates evaluated by Rules.

The interface text when entering dates for date comparison says to enter "The date in GMT", however the fixed or relative date entered is evaluated against the timezone in Regional settings, not GMT. Either the documentation needs to be corrected or the evaluation needs to work against GMT as documented.

Maintainers, what do you think?

Related issue: #1875866: Fixed date values drift by GMT offset when re-saved