[Outstanding bug list]

11 hours ago, the Seagnoid said:

Some of these bugs have been outstanding for years, and have been commented on in the forums numerous times.

 

Trackable ID error page does not help: Go Play > Trackables > enter an incorrect tracking id (the code on the trackable itself). This takes you to Geocaching > Trackable Items > Trackable Item Search, with the incorrect tracking id entered in the "By keyword" field. However entering a correct tracking ID in this field takes us to the same page. Either this page should not be used for incorrect tracking IDs, or the by keyword field should resolve tracking IDs.

 

Incorrect dates in souvenirs, lab finds - the date math is wrong and often (usually?) uses a date one day in the future. Eg, I find a cache on 1 January and I get the New Year's souvenir dated 2 January. Lab caches are also a day out as seen in their journals. At the time, the 2nd January has not appeared anywhere on the planet. Geocache date finds are calculated correctly, please use that date math (in fact, please use that date code) for souvenirs and lab finds. This may be time of day related, as some people report the dates correctly. This is a big one guys!!

 

Adlabs do not email the log (journal) to the CO. Why was this ever made into a thing???

 

Adlabs allow the CO to self log their own caches - a geocaching rule was implemented for non-labs caches preventing this around about 2016 (that's just a guess). This principle got missed on lab caches (and I would submit that self logged lab finds - and there are some - should summarily be deleted given that the code denying self logged caches was introduced long before lab caches were introduced. But then I am very black-and-white.)

 

Total cache find count for each friend in the View Friends page is incorrect. One whole cache type (lab caches) is missing from from the count.

 

There are probably more. Please feel free to add to this list.

Problem when you search from the main page on PC application Geocaching.com/play/search, you go back for any search to a list and sometime (not always) a map that list & represent cache around you registered location, not on the place you are searching for, this bug is reported since Nov (to my knowledge) and affect also search from a cache page when you try to find 'nearby caches' still today. Do all you technical people gone? Other sites are well better reactive to not name them

[Annoying emails from GC stating cache needs maintenaance]

A really bad algorithm in fact, (and i reported mine to geocaching.com in the first day of these feature, used on GS@k that do the job well better)

Today I receive such a false positive after a newcomer enter 3 times the DNF at same date for the same cache. The cache was found the same day by the same newcomer just before his 3DNF and found by another the day before. Mine take into account the D/T, watch 3 different days, by 3 different geocachers having a certain experience before triggering a warning

I understand why people were so sad when they distribute 'virtual' based on their 'algorythm'. This one also is certainly too simple

[Message Center - Browser not supported]

About 1 month that there are problems on this messaging feature. A pitty that even with all feedbacks (other conversation on this site) they cannot solve it. Don't hesitate to open each a formal problem report and get a ref number, may be they will react according the importance of users ennoyed

[Message Center misbehaving]

I just entered an officiel bug report on their site and get a reference number. Hoping it solves quick

[Message Center misbehaving]

Started since 21, serious annoying for us using this message center and begin to be long for correction.

Certainly not at the client side (because i use a lot different) but not even apologies on the message center page.

Where and how could I get a sign (formal from geocaching.com) that you are working on it?

[TB pour voyager]

si d'autres... ok si vous voulez faire démarrer un tb de Belgique.

Faite le moi savoir par mail direct sur geocaching en choisissant de laquelle de mes caches vous voulez qu'il parte. Je vous enverrai adresse

 

Pepegeo

[Pocket Query Attributes Issues]

When building pocket queries, I notice that:

o If you select "attributes to exclude" but do not select "attributes to include"

then the attributes to exclude are not saved.

o Example: Select only "exclude ticks". When I save the query and return to it, the ticks attribute is no longer selected.

o If I select exclude ticks and "include kid friendly" the problem goes away - both selections are saved.

Confusing

 

Thanks to forum and your message, i know now why when i tempt to filter out cache lasting more than 1h (selecting red bar on hourglass in exclude pane) i get the number of cache back when submitting, but it is not recorded. But your explanation is not true, excluded attribute seems to be never recorded in the query!

I tried include parking, exclude more than 1hour, it works at submitting, but when going back to list and re-entering the query, only the include is retained. I will start a new subject coz i don't know how to report such a bug. Could you help me?