openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #01987
Re: OpenERP : Timezone Glitch!!!
-
To:
openerp-community@xxxxxxxxxxxxxxxxxxx
-
From:
Stefan Rijnhart <stefan@xxxxxxxx>
-
Date:
Thu, 10 Jan 2013 20:11:30 +0100
-
In-reply-to:
<CANhvjXiHQ2C3Rb89fTUF3sRaLfpdhKER6t5=ty47u0AYFnqJHw@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
On 01/10/2013 07:40 PM, Mario Arias wrote:
At least for date fields, consensus was that system should record the
date as seen by the user creating the record, using the new
"context_today" method...
http://openerp-expert-framework.71550.n3.nabble.com/Bug-925361-Re-6-1-date-values-that-are-initialized-as-defaults-may-appear-as-quot-off-by-one-day-quoe-td3741270.html
That is, if someone on India creates an invoice on 1/10/2013 at 8am
his time, someone in America (12 hours behind in time zone) will see
in that moment the invoice as created in the future... and that is
good and expected...
Problem is that most addons are still missing this fix. You can check
bug report https://bugs.launchpad.net/openobject-addons/+bug/1073022
The suggested fix for this problem is an ugly workaround that would
actually work in a lot more cases if it was put in the context_today()
method itself.
The background problem is that the context is not passed on to the
workflow and the problem with fixing that is that not all methods that
are called from the workflow anticipate the context argument. Passing
the context argument could break a lot of things but now, at the
beginning of the cycle for 7.1 would actually be a great time to update
Olivier Dony's fix and merge it.
See https://bugs.launchpad.net/openobject-server/+bug/949516
Cheers,
Stefan.
Follow ups
References