Jump to content

Bug in new interface.


moonlighting

Recommended Posts

I am not trying to complain here...I really like most of the new changes and can live with the few that I don't. They are just going to take a little getting use to, but I would like to see a fix on something that has been bothering me since the new changes have begun to take effect. I just had a new cache published. On the Logged Visits, it shows 1 log entry (for the review published note) and then the new icons indicating the types of logs indicate two found logs and no publisher log. I am attaching a picture to point out what I am talking about. It would be nice to have these all zero'd out when the publisher publishes the cache and also subtract 1 from all the actual number of log entries that are shown to reflect a total number of logs that are from geocachers and not inlcude the published log entry in the Logged Visits count. Thanks.

geowebbugvf9.jpg

Link to comment

I'm not really sure why reviewer notes that are only seen by the cache owner show up in the list. Its not of any interest to the viewer.

I've also seen several new caches with logged visits saying 1, the 'found' icon saying 0 and then 2 people claiming FTF & 2nd find. This must be the same bug as the OPs

Link to comment

I believe that Logged Visits is just what it states, "LOGGED VISITS". Any log from Published, to Note, to DNF to Needs Maint... count as a written visit to the cache page. I believe that's why the new icon display has been implemented. If you count the numbers next to all those icons they should add up to the visits number, if not then there is some problem elsewhere such as deleted logs still counting since they are actually still in the database and can be read by anyone who knows the GUID URL.

Link to comment

We're aware of the issue and will be figuring it out today. Thanks!

 

Jeremy,

 

You said you thought this log count bug might be fixed on June 6th. It is now 8 days later, and I am still see bad counts all over. Can you please give everyone an update on this big bug fix. Thanks!

 

Here are easy to see errors:

 

http://www.geocaching.com/seek/cache_detai...88-43b66b1d5d03

 

http://www.geocaching.com/seek/cache_detai...52-e1172cc572e0

 

http://www.geocaching.com/seek/cache_detai...f5-d1a292708b5a

Link to comment
Guest
This topic is now closed to further replies.
×
×
  • Create New...