+caderoux Posted January 4, 2006 Posted January 4, 2006 http://www.geocaching.com/seek/nearest.aspx?state_id=19 Top few show as "unapproved" but you can click on them and they are clearly approved. Some kind of caching issue?
+The Leprechauns Posted January 4, 2006 Posted January 4, 2006 Yes, it is indeed a "caching" issue. The database with the geocache information is separate from the copies cached on the webservers. There can be a delay of a few seconds to a few minutes before the webservers catch up with the current database. So, for that period of time, you'll see published caches showing up as "unapproved."
+4leafclover Posted January 4, 2006 Posted January 4, 2006 wow... should that link still show? I mean, are there issues with allowing the "general caching public" to see unapproved caches?
+4leafclover Posted January 4, 2006 Posted January 4, 2006 okay...never mind... they may still be named unapproved, but it looks like they are indeed, approved. sorry.
+Jeremy Posted January 4, 2006 Posted January 4, 2006 There's something wrong with replication at the moment. I'm looking into it now. Thanks for the info.
+Jeremy Posted January 4, 2006 Posted January 4, 2006 I reset the transactions and they seem to be working now. I think the activity of logging caches on Tuesday really took the server on a wild ride.
+Teamhawaii1981 & blueicyrose Posted January 4, 2006 Posted January 4, 2006 I reset the transactions and they seem to be working now. I think the activity of logging caches on Tuesday really took the server on a wild ride. It probably has something to do with increased activity; but another similiar problem is that logged caches did not show up as checked off in the search pages for me after logging today.
Recommended Posts