You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: orrc [Submitted to the original trac issue database at 11.51pm, Sunday, 13th December 2009]
It seems that currently (Potlatch 1.3b) is somehow reporting the wrong time when uploading a changeset after working in offline mode. The closing time is always one hour ahead of the starting time.
In each case, the editing time is exactly one hour (plus a handful of seconds).
I would note that I am currently in CET (+0100), and my computer's clock is set as such. The start time is correct, taking into account the fact that they are shown in GMT (+0000).
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 6.50am, Monday, 14th December 2009]
This is what's meant to happen. Changesets time out one hour after the last edit. If you want to manually close a changeset, press C or use the option in the Advanced menu.
Reporter: orrc
[Submitted to the original trac issue database at 11.51pm, Sunday, 13th December 2009]
It seems that currently (Potlatch 1.3b) is somehow reporting the wrong time when uploading a changeset after working in offline mode. The closing time is always one hour ahead of the starting time.
Here is a changeset I did in offline mode with Potlatch earlier today:
http://www.openstreetmap.org/browse/changeset/3368345
Here's a random changeset I pulled from recent history:
http://www.openstreetmap.org/browse/changeset/3368713
In each case, the editing time is exactly one hour (plus a handful of seconds).
I would note that I am currently in CET (+0100), and my computer's clock is set as such. The start time is correct, taking into account the fact that they are shown in GMT (+0000).
The text was updated successfully, but these errors were encountered: