[bug] Logging date doesn't stick

[+T0I3145]

I also have the same problem. I log normally on next day (after a cache tour)

[+Harry the furry squid]

Same problem here. What's happening is that one used to be able to just change the date once at the start of a logging session, and the logs would then carry on defaulting to that date for an hour or so or until you changed it. That seems to have stopped working, so each and every log has to be changed manually from the current date.

[Frau Potter]

We are aware of the issue and have brought it to the attention of the engineering team. We know that some recent changes were made to help prevent other problems on the website. 

[+fyntastic]

Is there any news on this topic? Last night it was still not working correctly.

[+seedcorp]

Any progres?

[Frau Potter]

We don't have a timeline, but I have heard from engineering that they are looking into fixing this. The current implementation is no longer possible due to cookiebot issues so we are seeking a new solution. Please be patient.

[+terratin]

And another bug. Logging caches from last weekend from a list. I opened the list on a map as usual and when I open the cache page, or go directly to LOG from there I always get today's date with every log. In the past the last chosen date would stick on the log form for a while.

Windows laptop, Firefox (about two updates behind)

[+terratin]

7 minutes ago, HHL said:

See that:

 

 

Ah, so that bug is the same. Didn't realize just from the title (so many caches to log, so little time!). And still not fixed then. Thanks a lot.

Edited May 13, 2023 by terratin

[+bd's]

I've been having the same problem. It's very annoying and also very time consuming to have to go back and edit everything. I hope that this gets fixed soon. It seemed to work quite nicely in the past.

[+Optimist on the run]

Still not working. Please revert this to the way it used to work.

[+fyntastic]

Any news, Mrs. Potter? Or anyone, for that matter?

[+fyntastic]

When I post logs for trackables, the date does not change back to today. After I post a log for May 16th, the next log will automatically be set to May 16th too, for instance. So there is a way to make this possible.

[+GrossATuin]

Unfortunately it still doesn't work & it's so time-consuming ... I could use the time to create new geocaches ...

[+fyntastic]

Any news on this topic? The date works fine when I log trackables, so I don't see what the holdup is regarding cache logs.

[+Alphadog]

Same problem. Is it going to be fixed? It’s been at least a month now. 

[Frau Potter]

I checked with the engineering teams and this is still in the process of being worked on. We haven't forgotten!

[+terratin]

Thanks a lot Frau Potter. This is a super annoying problem as I'm very behind with logging caches at the moment. I continuously have to edit the found date when i get to logging.

[+Optimist on the run]

It's now been two months and it still isn't fixed. This is no longer merely frustrating; I am now getting angry that Groundspeak don't seem to care. It should be a simple bug to fix, but all they seem to care about is setting more and more ridiculous souvernirs. I have 31 caches to log today that I found yesterday, and will have to waste time fixing the date on every one.

[+fyntastic]

What annoys me is that it works fine with trackables. Whatever the code is over there with trackable logs should work with cache logs as well. It's likely not as simple as copy & paste, but surely not far from that.

[+T0I3145]

With the old log site "style" it works fine, with the new "style" the date jump always to the actual date

[+seedcorp]

On 6/23/2023 at 4:57 AM, Frau Potter said:

I checked with the engineering teams and this is still in the process of being worked on. We haven't forgotten!

 

One month plus, working hard on it?

[+bd's]

This is now around 2 months since this issue started. I'm trying to log my finds from a recent mega event which is proving to be very difficult. Any news on the resolution to this problem? It sure seems to be dragging on a long time.

[+Rampensau]

On 7/25/2023 at 2:08 PM, bd's said:

Any news on the resolution to this problem?

 

Quote

this is still in the process of being worked on

 

;-)

Edited July 31, 2023 by Rampensau

[Frau Potter]

Sorry for the delay, but I can confirm that the team is still exploring options to make the log date sticky again and does plan to roll this out once they have completed the coding and testing. 

[+Gilrond]

Still not working...

A bit frustrating when trying to log tens of caches found few months ago.

[+lefisher]

It really is a nightmare to keep changing the date.  I have had to go back over some of my logs to change the date when I logged the day after finding them.  Please, please get this changed.

[+BigFurryMonster]

Please please fix this! I'm logging a bunch of caches found during my holiday, and it is annoying to change the date for each log.

[+seedcorp]

Another month plus. WTF? Please fix it asap. (Here should be thanks, but...)

[+Viajero Perdido]

Click the "Opt out" link in the upper-right corner to disable this behavior.

[+seedcorp]

Old logging page remebers tha date, but you have to select type of log on every page, it does not remember type of log... so the problem is the same...

[+Optimist on the run]

Over four months now. I'm told by an expert that all that's required is setting a session cookie, so I really don't understand why this still isn't fixed. Do Groundspeak even care?

[+Optimist on the run]

On 7/31/2023 at 7:03 PM, Frau Potter said:

Sorry for the delay, but I can confirm that the team is still exploring options to make the log date sticky again and does plan to roll this out once they have completed the coding and testing. 

@Frau Potter Can you confirm that the team is still working to fix this annoying bug? 5 months and counting, and though there is the get-around of using the old logging system, having to set the log type every time is almost as annoying as remembering to change the date with the new system.

[+bd's]

I've decided that I don't care what date my caches are logged on. It the date won't stick I'll just log everything on whatever date shows up. I'm planning a trip soon where I might find up to 100 caches. I have no plans to keep changing the date for that many caches.

[+niraD]

2 hours ago, bd's said:

I've decided that I don't care what date my caches are logged on. It the date won't stick I'll just log everything on whatever date shows up. I'm planning a trip soon where I might find up to 100 caches. I have no plans to keep changing the date for that many caches.

[+the Seagnoid]

Still not fixed :-(

 

Could we PLEASE ask the engineering team to stop work on new projects and fix the annoying bugs in the existing products?

[+seedcorp]

Another month... pleeeeeeaseeeee pleeeeaseeee fix it. How complicated could this issue be? On lots of other pages it works... so pleeease pleeees, dont take me mi down...

[+Optimist on the run]

On 10/14/2023 at 10:24 PM, bd's said:

I've decided that I don't care what date my caches are logged on. It the date won't stick I'll just log everything on whatever date shows up. I'm planning a trip soon where I might find up to 100 caches. I have no plans to keep changing the date for that many caches.

I like to keep logs with the correct dates, but I'm now considering logging everything as I go using the app, rather than trying to write proper logs using a keyboard when I finish. It means logs will just be "TFTC", as I hate trying to write long texts on a crappy phone keyboard.

 

Seriously, why is this such a problem?

[+niraD]

3 hours ago, Optimist on the run said:

I like to keep logs with the correct dates, but I'm now considering logging everything as I go using the app, rather than trying to write proper logs using a keyboard when I finish. It means logs will just be "TFTC", as I hate trying to write long texts on a crappy phone keyboard.

[Frau Potter]

Please see the Release Notes (Website: New geocache and trackable logging flow) - November 2, 2023 thread about how this will be fixed, as soon as you have access to the new log flow. 

[+bd's]

Well, today I got a new logging screen that fixed the date issue. Now the log type doesn't stick and I can't upload any pictures. I'm not sure why something that was working perfectly a few months ago had to be fixed.

[Keystone]

@bd's, you should post details about your experience in the Release Notes thread linked to by Frau Potter in the post above yours.  I've been using the new logging flow for 100+ logs, and I haven't had problems with either the log type "sticking" from my drafts, or in uploading images.

[richlv]

I always used the "old" logging form, and it nicely preserved the previously selected date (until day change in the USA, I believe).

It looks like the "old" form has been removed now (don't see the opt out link anymore), and I'm stuck with the new form, which does not preserve the date.

 

Can we please get the old form back? It worked better

[Keystone]

As noted above, this should be discussed in the current Release Notes thread.  The opening post in that thread points out the method for making the log date "sticky."

 

The new logging flow will be the only method going forward, so any bugs or enhancement requests should be pointed out in the Release Notes discussion.

 

At this time, I'm closing this thread as redundant to the Release Notes.