Can't log anything

[Nylimb]

I just tried to log a cache, and it didn't work.  As soon as I clicked on "Log geocache" from the cache page, the form to create a log appeared in my browser, but it disappeared in a fraction of a second, replaced by a blank window.  I've tried this several times on both caches and trackables, with the same result.  If I press the escape key as soon as the form appears, I can sometimes prevent the blank window, but the form doesn't work: Clicking the arrow for selecting the log type doesn't show the menu of options.

 

I'm using Firefox version 78.15.0esr (64-bit) under Mac OS X 10.11.

Edited November 13, 2023 by Nylimb

[+Bl4ckH4wkGER]

Both your operating system and your web browser versions are several years old.  Your browser version for example was released on June 30, 2020. Your operating system is even older.

 

A guess could be that the new logging flow release requires technology that's not offered or supported by these old versions.

 

I'd recommend trying a different browser to start.

[ColleIsarco]

Same issue here and no it is neitehr an old browser nor an old operating system.

 

Regards

[ColleIsarco]

4 hours ago, Nylimb said:

I just tried to log a cache, and it didn't work.  As soon as I clicked on "Log geocache" from the cache page, the form to create a log appeared in my browser, but it disappeared in a fraction of a second, replaced by a blank window.

You can use the old log-page by using this link: https://www.geocaching.com/seek/log.aspx?wp=GC12345

Replace GC12345 wit the waypoint-name

[Nylimb]

1 hour ago, ColleIsarco said:

You can use the old log-page by using this link: https://www.geocaching.com/seek/log.aspx?wp=GC12345

Replace GC12345 wit the waypoint-name

Thanks, but that doesn't work for me either.  It fails in the same way as I described earlier.

[+janrei_]

Is it possible to try a different or more modern browser, as suggested by Bl4ckH4wkGER?

 

The current implementation of the new logging flow seems to require a fairly recent version of Firefox.

[ColleIsarco]

3 hours ago, janrei_ said:

Is it possible to try a different or more modern browser, as suggested by Bl4ckH4wkGER?

No, it is not! And actually I don't want even to use the new log-page I want to stay on the old one, which works perfectly fine, but any reason the opt-out does no longer work.

[Nylimb]

18 hours ago, janrei_ said:

Is it possible to try a different or more modern browser, as suggested by Bl4ckH4wkGER?

I'm not sure.  Based on what I've found online, I think I could upgrade my operating system to 10.12 but nothing beyond that.  But I haven't determined what version of Firefox (or some other browser) that would let me run, and I don't know what version is required for the new logging flow.  I'm reluctant to take the time and risks of upgrading unless I'm pretty sure it would solve the problem.

[+janrei_]

If you can upgrade to macOS 10.12, I would give it a try.

 

Firefox 115 ESR supports this version of macOS and is still receiving security updates. See the introduction in the release notes:
https://www.mozilla.org/en-US/firefox/115.0/releasenotes/

 

I think Firefox 115 should be recent enough to work with the new logging flow.

[+Hynz]

On 11/13/2023 at 6:09 AM, Bl4ckH4wkGER said:

A guess could be that the new logging flow release requires technology that's not offered or supported by these old versions.

I know it's not fully Groundspeaks fault but I can't help regretting this development of webdesign.

Even on new technology it needs absurd CPU power and often is accompanied with breaking old and good conventions.

[Nylimb]

14 hours ago, janrei_ said:

If you can upgrade to macOS 10.12, I would give it a try.

 

Firefox 115 ESR supports this version of macOS and is still receiving security updates. See the introduction in the release notes:
https://www.mozilla.org/en-US/firefox/115.0/releasenotes/

 

I think Firefox 115 should be recent enough to work with the new logging flow.

Thanks for the info.  I might try that, if gc.com doesn't fix the problem.  For now, I've found that I can log caches using a borrowed smartphone, so at least I have a workaround.

[+Mutex]

Soo.. It's been a while since this problem started and I still get a blank screen when trying to log a cache or travel bug. The link provided by ColleIsarco also does result in a blank page.

On mobile works, but is just not as comfy.

 

Win 10, 64bit, latest, Firefox 121 with various extensions - no log possible

Firefox 124, brand new, not modded at all, on a completely fresh win 10 - no log possible

Chrome 120 - no log possible

Edge (Yes, I tried it) - no log possible

 

Interestingly enough I just found out that only clicking on the 'log geocache' button in the listing does result in a blank page. Opening the logging page via a draft works fine.

Clicking on a 'log geocache' button gives an URL like this: https://www.geocaching.com/seek/log.aspx?ID=7487274&lcn=1, which results blank

Clicking on a draft gives an URL like this: https://www.geocaching.com/live/geocache/GC8H3XX/draft/LDA5433K/compose, which works

I'm no hardcore tech guy, but I'd say, as logging is still possible via drafts, there is something wrong with the generated link applied to the log/discover button.

 

Soo.. Hello Groundspeak, it's at least three months! Does anyone at HQ care?

[+janrei_]

Since the problem originally reported in this topic only occurs with outdated browser versions, it is probably not a high priority for Groundspeak. However, the browsers you have tried are up-to-date and should work.

 

The "Log geocache" button still links to the old logging form, but you should be redirected to the new one immediately. In your example this would be https://www.geocaching.com/live/geocache/GC8H3XX/log. Does this link work for you?

[+janrei_]

I have noticed that an update has been deployed which should improve browser compatibility. So if you had problems with the logging form not loading correctly, this might work now.

[Nylimb]

5 hours ago, janrei_ said:

I have noticed that an update has been deployed which should improve browser compatibility. So if you had problems with the logging form not loading correctly, this might work now.

I just tested it, and I can indeed create and edit logs again.

 

Thanks for the post!

[+Mutex]

On 1/11/2024 at 12:16 AM, janrei_ said:

Since the problem originally reported in this topic only occurs with outdated browser versions, it is probably not a high priority for Groundspeak. However, the browsers you have tried are up-to-date and should work.

 

The "Log geocache" button still links to the old logging form, but you should be redirected to the new one immediately. In your example this would be https://www.geocaching.com/live/geocache/GC8H3XX/log. Does this link work for you?

 

Yeah.. the 'it should work' part is the one that bothers me. During last weeks holiday I logged mobile via c:geo which still works fine. Now, back home, I tried logging with firefox again and it still opens a blank page.

Interestingly enough there is a change. Now, maybe since the mentioned update, opening the logging page from a draft also results blank. Meeehhh...

Also the 'view log' and 'view your log' buttons link to the old page. So editing logs is also not possible. Can't recall, if this worked before my holidays.

 

The link you provided works. So I'll probably just have to write myself a little macro to add the /live and /log to my URL. And then wait ':|

 

Thanks for your help