geoconsumer

Local first! Follow the conventions of your area. If you don't know it, I suggest you log your find (weather FTF or not) asap. Even if it's a temp log. This is as a courtesy to other cachers who might be on the way or considering going. Gas is $. As a side note: I have to say you spent more money on gas to get to the cache then you would on data. Temp Logs: As a courtesy to the Cache Owner, I suggest posting a note with your updated log contents or delete your original log and post a new log. Notifications for owners are only sent when a log is created, not updated.

There seems to be a change with trackables: * The order of the logs seems to be ascending for each day. See TB3AHM3. Find #241 is listed before #237, which should happen because #241 was found later in the year. But #237 is before #240. #237 and #240 are on the same day. #240 occurred and was logged after #237 but is being listed after it. This is a change in functionality from the previous release that makes the log order appear inconsistent. I noticed this before I logged a find and noticed.... * TB3AHM3 was picked up, yet it doesn't show up in the log. It now can't be picked up as, it's being help by owner. (Retrieve log is now showing up). One might dismiss this as user error (it still might be), but also note that I recalculated the distance and took a closer look as I noticed the milage was not calculated and the retrieve was missing. * The milage for TB3AHM3 on 3/31/2010 is missing, even though a 'recalculated distance' was executed. This might be because the log that the trackable was dropped with was archived. This is a change in functionality from the previous release. Unrelated to trackables, but also important, I'm getting a lot more 500 - Internal server errors when going through the site.