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 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.