scheduler expects field times in UTC/GMT when they are actually stored in local time

Hi Fago,

Thank you for your response, all your coding work on entities, and especially your attention to the issue queues!

The goal is to send out an email 5 days before a date as set in a field.

The scheduler component has a "scheduled evaluation date" using a data-selector of the date field. There is no direct input for this, thus no token availability.

Below that, in the "add offset" section, I have -5 days. But, as mentioned, it is subtracting 5 days from the date with the expectation that it is stored in GMT, when in fact it is stored in local time.

In the offset section, there is the option to use direct input with a value that gets fed straight into strtotime(), and as the context help says, one can use strtotime's offsetting directly, but here too strtotime() is expecting a GMT date, as also stated in the context help.

But you know, the more I think about this, the more I realize that it's understandable that rules expects dates to be stored in GMT/UTC. Trying to patch rules to account for timezone would mean that it would have to find out from date how a given date field is stored, which may not be trivial. I'm going to call this issue null, and simply change my date fields to store via UTC....

Thanks for your attention in any case!!

Shiraz