Lissi&Gusti

With hindsight, and with the suggestions from others in the thread, I'm going to add to the list (while quoting myself to keep it all in one post). An explanation of the team split and re-logging on your old and new profile pages (in addition to the "etiquette note"). If using GSAK to re-log: run it for a few caches, and then go check the results for formatting. Then wait, to give cache owners a chance to react, and mabe show what you might phrase more clearly and transparently. Note that a log deletion will also make any photo that you posted with your log unavailable, and you may need that photo to support your claim that you actually found the cache. If a cache owner deletes a log, you will either have to re-log it (ideally after coming to an understanding with the cache owner) or ask HQ to reinstate/unarchive the log. The cache owner has no way to reinstate the deleted log.

When entering a "Geocacher disagreement" because of "Geocache log deletion", HQ responds with a mail titled "Geocaching log deletion questions" and a number in curly brackets {.......} with eight questions. These are to be answered in order, in no more than three sentences. I contacted HQ because of two log deletions, sending the requests within minutes of each other. I received two mails requesting the 8 answers, differing only in the {number} in the Subject line. I can't tell which set of answers goes with which request! I ended up guessing, using the timing as a guide. (There is also a reference to a link in the mails to enter these answers -- that these links are missing is the subject of another bug report.) I would like an indication of which request the mail applies to. Thanks, Gusti

You did not check my account, you checked the new one -- *I* did not write that etiquette note. That's why I wrote to make it expanantory and multilingual. Placing info into the new profile is a good one! Some owners deleted the original logs as well as the new one. Some owners deleted not only the old original logs, and also the logs of other cachers mentioned in those logs, logs that were entered many years ago. All deleting owners received a long explanation immediately after their deletion message. Where I still could remember, or where I had noted it, I added details of the hide that only someone who had really found it would know -- details that the log didn't mention because it would spoiler the hide. In one case I pointed out a log by some cachers I had met while searching who mentioned meeting me. *None* of these owners responded, much less reinstated the original log. Gusti

Thanks, Keystone. I wrote, and HQ reinstated the logs! This seems to be one of the more recent threads on the topic of team account split, separation, relogging team caches found as an inidvidual or however you'd describe it. I'll wrote down what I learned... Make that "etiquette note" as explanatory and detailed as possible! If you cached different countries: use a translation service to translate it into the local language of any caches you found. GSAK allows sorting by country, so one could log with an appropriate text, or one could use the same text for all, but then include several languages in the note. Some owners will delete the new logs anyway: because it's long ago, archived, looks suspicious, ... Some owners will delete the new logs, the original logs, and also the logs of any folks who you mentioned in your log as well. Having copies of the original logs helps -- so keep a copy of the orginal "My Finds Pocket Query", or some other record. You will receive a mail notifying you of any deletions. Some owners will write and ask the original account owner if the new log(s) is/are legit, so be prepared to be answering messages. Don't wait and let these folks worry you've been hacked -- these will tend to be folks that know you! Odd "edge cases" *will* turn up: Caches with DNF logs. "Will Attend" logs at event caches with a waiting list that you didn't make, and so never "attended", "write note", ... deal with it:-) To get deleted logs reinstated, HQ will ask: where/which cache, who's involved, log date, and any proof that you were really there. This could be photos, other cachers, a description of the container or location, bonus numbers, answers to questions, etc. Gusti

Okay -- I'm running into trouble here... not with the process but with some owners. I have the old account. We found some caches with our children who have their own account: P+M, basic membership, and pretty much inactive now. Now the GSAK macro is currently logging the new account. One owner deleted the new logs, the original logs, and the children's logs as well, as they were mentioned in the original log, citing that they suspect cheating. (We would find a cache, write and post a log, and then log the kids with a simpler "found it with Lissi&Gusti"...). I have asked the owner to reinstate logs, but haven't had a response -- to be fair, this was only a few minutes ago. Another says "this isn't fair, no way can one re-log a cache!" And that they will delete the new logs... I responded by saying that this is at Groundspeak's suggestion. Gusti

Keystone, could you add some info on the "edge cases" in this process? Some of these are: - it is possible to re-log archived caches (I think that's a "yes") - it is possible to re-log locked caches (I think that's a "no") - and are there any that can't be transfered -- benchmarks? (I do use GSAK -- also, as a note to Team Moxiepup: GSAK is now free, but wasn't at the time some of the threads were written). Gusti

I'm seeing the blinking icons right now, on th "print" versions of a cache listing page: https://www.geocaching.com/seek/cdpf.aspx?guid=e6815e1c-0a48-431d-a946-60a78a6f90e7 https://www.geocaching.com/seek/cdpf.aspx?guid=3cde9a10-c0b5-485b-922a-31bcd1603921

I have looked at my GSAK database for some caches that have names I'd class as "possibly difficult", and searched for them using "Search with filter", "Geocache Name Contains ..." and "Searching without a location". These work, and are found in the search: GC6B8W0 قهوة GC4M52B συναισϑάνομαι GC531VV Ночной Дозор These don't: GC6DTXQ ² GC4XY7M . GCMM7M ? GC3HC6G ...... GC355Z2 .--. ..- --.. --.. .-.. . -.-. .- -.-. .... .

That makes sense. It still doesn't work, at least not now. Both + and & in the "Geocache Name Contains ..." filter field lead to: "Oh no, a DNF! We couldn't find any geocaches that matched your search." Since it very clearly worked for you, I'm guessing there's some behind-the-scenes code tuning going on.

Entering a "&" (ampersand) into the new global search causes a server error 500. Entering a "+" (plus) returns 21 caches, none of which appear to contain a "+" in their name. Why would I want to search for such caches? There is a challenge cache which calls for one to spell one's caching nick with the initial letters of found cache names. Our nick contains an &, another team we cache with has a + in their nick... (xkcd 327, btw.) Lissi&Gusti

I'm getting this error where logs contain the string "ERROR: Method not found" and broken HTML code. It appears to happen when logs contain a link. I can't ewll if it's broken by the logger or somewhere downstream. (I've xxx-ed out the nonessential information.) (And yeah, it likely wouldn't have happened with a text-only email, which I would prefer...) "Plakativ! (GC56P6H) has a new log: Logged by: xx Log Type: Found it Date: 8/16/2014 Location: Bayern, Germany Type: Traditional Cache Log: XXXX <p[ERROR: Method not found: 'Int32 System.Environment.get_CurrentManagedThreadId()'.]Besucht uns auf http://www.Gutenberg-2015.de <br[ERROR: Method not found: 'Int32 System.Environment.get_CurrentManagedThreadId()'.]

I dont know how long this has been like this, in a "[LOG] Owner" email: "© 2000-@DateTime.Now.Year Geocaching, a Groundspeak, Inc. Project. All Rights Reserved." but "@DateTime.Now.Year" looks like a broken variable, dunno at which end. Please bring back text-only emails, possibly as an option.

Please bring back plaintext email as an option.

My strong vote for a) plain text a maximum of terse information in the "Subject:" line. I am member of a team providing a "cache maintenance service" for cache owners during an upcoming Giga Event. Along with advice on dealing with large numbers of searchers and finders, we offer to perform maintenance for owners who are unable to maintain themselves during the event. This is so that folks coming to visit will have lots of well-maintained caches to find, instead of a desert of caches set to TDA because of possible cacher overload. This is planned for up to 600 caches with up to 10.000 attendees. Only an unpredictable fraction of attendees will be out finding and immediately logging these caches. But there will be a huge number of emails to automatically sift for "needs maintenance" logs, in something that needs to approximate real time -- we need to know that Cache XY "needs maint" within minutes, not days. This is a task which is manageable with the info needed in the subject line. Parsing the body of a mail is a more difficult and slower task. And it breaks a system which was running and had so far successfully processed about 60.000 logs in a trial run. 60.000 links to instagram, google play -- naah, don't need that. I can't repeat what the IT guy said as the system broke yesterday, because it'd (rightly!) get this post deleted. Please, Groundspeak developers, remember this: It is an outdoor sport. Think of some cacher out in the woods, in mountains, stuck between skyscrapers. They are climbing a tree and holding up their phone on a stick in the hope of getting some sort of data connection. Just hoping for enough bits to dribble through to read some logs for a clue, check for a spoiler picture, to make sure the cache hasn't been archived or disabled... The geocaching notices and links are "preaching to the choir", folks, and those cachers will be happier with less data! And all those cachers holding the phone out of a ravine on a stick are happy that you introduced a "terse text" function for email communication.

This extends to the log emails as well, I got this as subject line in an email: This previously would have read "(Unknown Cache)". And while they are commonly referred to as "mystery" caches, the have always been "unknown" in the log mails. Please revert this, it breaks things... Gusti

As a cache owner, I can mark a TB missing with a special "mark missing" log type. However, there is no way to edit the automated message -- I get a "you can't do that" message. So, any comment must go in a separate note? Please make this message editable, or am I missing something? Also the help says: I find this confusing because one can log the note without the reference number -- one wouldn't usually have the number if the trackable is missing, right? Happy Holidays!