Site Update February 12, 2024

[Corfman Clan]

Hi,

I have just updated LonelyCache.

There was a problem where some finds would be missed when a cache was fully updated. This occurs every four months. I am pretty sure I have fixed the cause of the problem. However, any caches where this occurred may not include the missing finds for up to four months from now. If you notice a cache where your find is missing, then sync the cache and the missing logs will be added.

For subscribers, I have again updated the geocache page. Subscribers now can add or remove the cache from their watch list. Also, how the user notes are displayed has been updated.

Enjoy,
Russell

[Corfman Clan]

Hi, I made another quick update to change how logs are sorted on the Geocache Page, and to ensure that FDF points are only shown with found-it logs.

[UsLaynes]

I seem to be having an error pop up on all the pages. When I click on "Your found/owned", "Your not found/owned", "Longest Alone", or, "Longest Unfound", I get the message "The page cannot be displayed because an internal server error has occurred.". I tried those options on Counties, States and all of LonelyCache. Glad to see many of the other things being fixed, and hope this one can be fixed soon.

Thanks
UsLaynes

[Corfman Clan]

I seem to be having an error pop up on all the pages. When I click on "Your found/owned", "Your not found/owned", "Longest Alone", or, "Longest Unfound", I get the message "The page cannot be displayed because an internal server error has occurred.". I tried those options on Counties, States and all of LonelyCache. Glad to see many of the other things being fixed, and hope this one can be fixed soon.

Thanks
UsLaynes

I see the same thing. Thanks for pointing that out. I'll try to get that resolved soon.

[Corfman Clan]

I seem to be having an error pop up on all the pages. When I click on "Your found/owned", "Your not found/owned", "Longest Alone", or, "Longest Unfound", I get the message "The page cannot be displayed because an internal server error has occurred.

This is now fixed.