Jump to content
Sign in to follow this  
Followers 2
rapidkhan

Logs one day out when using the drafts

Recommended Posts

Whenever I use the 'Draft' function I use them like the old field notes where I put a little reminder of which cache I found.

 

When it comes to post the log in the app, it logs it as the day before.

This is a big problem and I have had to go back and manually change a bunch (the last month or so) of logs to the correct date.

Share this post


Link to post

Whenever I use the 'Draft' function I use them like the old field notes where I put a little reminder of which cache I found.

 

When it comes to post the log in the app, it logs it as the day before.

This is a big problem and I have had to go back and manually change a bunch (the last month or so) of logs to the correct date.

 

There was comments posted from others in the Release Note thread about this problem starting at http://forums.Groundspeak.com/GC/index.php?showtopic=343515 starting around post #27 . You are not alone in experiencing the issue.

Share this post


Link to post

TPTB seem to be aware of the timezone issues and they announced that there will be changes next month that will hopefully remedy those issues. The announcement was distributed to API partners, but Team DEMP copied it into this post.

Share this post


Link to post

Don't count on it. Wrong date logging has been an issue for ten years.

Share this post


Link to post

Don't count on it. Wrong date logging has been an issue for ten years.

So pessimistic. They've announced that they've worked out a solution, so how about giving them a chance to address an issue that cachers have been asking them to address - rather than just writing it off. I'd be pretty unmotivated to work on requests if the response was so negative about everything. Or maybe they just shouldn't work on it, since it's already been 10 years?

Share this post


Link to post

Don't count on it. Wrong date logging has been an issue for ten years.

So pessimistic. They've announced that they've worked out a solution, so how about giving them a chance to address an issue that cachers have been asking them to address - rather than just writing it off. I'd be pretty unmotivated to work on requests if the response was so negative about everything. Or maybe they just shouldn't work on it, since it's already been 10 years?

 

Ten years seems a long time to have such an issue and not deal with it. It's not so bad if you live in USA but if you live in NZ where we are first in the world to start the new day, only those logs that are posted late in the evening are logged on the correct day. This makes for a long exercise of changing dates manually for the sake of accurate statistics. Perhaps Stegan and I can be excused for being a little impatient?!

Share this post


Link to post

Perhaps Stegan and I can be excused for being a little impatient?!

Being impatient is fine. It's another matter when someone appears to doubt that Groundspeak is being truthful about their intentions.

Share this post


Link to post

Wow, people complain about the lack of time zone support for years, and when Groundspeak finally announces that they're dealing with it, the people complain about that?

 

I guess they can't win...

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 2

×