Mr.Yuck Posted February 1, 2009 Posted February 1, 2009 Exactly what the title says. If you are a casual user that goes months or even years without logging in to geocaching.com, apparently you need to be logged in for a good long time (maybe an hour), or else "last visit" in your profile will not be updated. Not me of course, I'll bet I have quite the consecutive day login streak going. But I first noticed this a couple of months ago when some guy with like 10 finds in a three year career logged one of my Earthcaches. His last visit in his profile was (and probably still is) June 2008. So then I've noticed it a couple more times, and even experienced it with a seldom used family member account. I even logged a cache as a find for them, was logged in for a good 15 minutes, but it never updated in the profile. But seeing as I had seen this, I re-logged in, and left the computer set for about an hour, and it updated. Or perhaps it was the fact I logged in twice on the same day. Not a big deal in the grand scheme of things I suppose, but this is definitely happening.
+StarBrand Posted February 1, 2009 Posted February 1, 2009 I have also seen that once or twice but shrugged it off as a fluke.........occasional cachers that had logged one of mine but profile had a much older date.
Mr.Yuck Posted February 1, 2009 Author Posted February 1, 2009 If anyone has a sock puppet OOOPS ERRRR I mean seldom used family member account, feel free to try this out. I have seen a previously seldom used account log 15 caches as found this month, but their last log in date is almost a year ago.
OpinioNate Posted February 3, 2009 Posted February 3, 2009 Nice find. After some testing it looks like this only happens when you login with the widget on the front page. It doesn't matter how long it's been since you last logged in, but you're probably right that it will eventually update if you stay logged in long enough. I'll have to play around with it a little more to figure out when that happens. Thanks for pointing this out. It explains another bug I had open where someone visited a PMOC (audit logged) but hadn't logged in to do it!
+pppingme Posted February 4, 2009 Posted February 4, 2009 Nice find. After some testing it looks like this only happens when you login with the widget on the front page. It doesn't matter how long it's been since you last logged in, but you're probably right that it will eventually update if you stay logged in long enough. I'll have to play around with it a little more to figure out when that happens. Thanks for pointing this out. It explains another bug I had open where someone visited a PMOC (audit logged) but hadn't logged in to do it! Huh, I pointed this out a month ago and got a rude response saying it was a known problem and they were fixing it.
+benh57 Posted February 4, 2009 Posted February 4, 2009 (edited) Nice find. After some testing it looks like this only happens when you login with the widget on the front page. It doesn't matter how long it's been since you last logged in, but you're probably right that it will eventually update if you stay logged in long enough. I'll have to play around with it a little more to figure out when that happens. Thanks for pointing this out. It explains another bug I had open where someone visited a PMOC (audit logged) but hadn't logged in to do it! Huh, I pointed this out a month ago and got a rude response saying it was a known problem and they were fixing it. Keystone's reply doesn't appear rude to me (which they often do), but what is unexplained is why Keystone said Groundspeak is looking into it when he isn't Groundspeak. So, Keystone apparently was misinformed. http://forums.Groundspeak.com/GC/index.php...=209905&hl= Edited February 4, 2009 by benh57
Mr.Yuck Posted February 4, 2009 Author Posted February 4, 2009 Nice find. After some testing it looks like this only happens when you login with the widget on the front page. It doesn't matter how long it's been since you last logged in, but you're probably right that it will eventually update if you stay logged in long enough. I'll have to play around with it a little more to figure out when that happens. Thanks for pointing this out. It explains another bug I had open where someone visited a PMOC (audit logged) but hadn't logged in to do it! Huh, I pointed this out a month ago and got a rude response saying it was a known problem and they were fixing it. Keystone's reply doesn't appear rude to me (which they often do), but what is unexplained is why Keystone said Groundspeak is looking into it when he isn't Groundspeak. So, Keystone apparently was misinformed. http://forums.Groundspeak.com/GC/index.php...=209905&hl= Sorry, didn't mean to cause any trouble. I admit to not doing a search of this forum, although how would I know what keywords to use? I do think Keystone was rather cheerful though.
Keystone Posted February 5, 2009 Posted February 5, 2009 An inaccurate "last visit" date is of particular importance to volunteer cache reviewers. We use this information when making decisions about cache maintenance issues. It should, therefore, come as no surprise that the volunteer cache reviewers raised this issue with Groundspeak last summer. The issue was documented as Bug #6034 last year. Therefore, my post referenced above was not "misinformed." I have taken note that the inquirer found that reply "rude." I will avoid responding to further questions from that poster so as not to upset them.
+pppingme Posted February 5, 2009 Posted February 5, 2009 Nice find. After some testing it looks like this only happens when you login with the widget on the front page. It doesn't matter how long it's been since you last logged in, but you're probably right that it will eventually update if you stay logged in long enough. I'll have to play around with it a little more to figure out when that happens. Thanks for pointing this out. It explains another bug I had open where someone visited a PMOC (audit logged) but hadn't logged in to do it! Huh, I pointed this out a month ago and got a rude response saying it was a known problem and they were fixing it. Keystone's reply doesn't appear rude to me (which they often do), but what is unexplained is why Keystone said Groundspeak is looking into it when he isn't Groundspeak. So, Keystone apparently was misinformed. http://forums.Groundspeak.com/GC/index.php...=209905&hl= I should add, I didn't say the rude response was in the forums, but to that I'm not going to exclude or defend any particular name either. I do find it interesting though that actual staff doesn't even seem to know about it until now yet some forum moderator who isn't staff says its a known bug.
Recommended Posts