+Spacemann Spiff Posted August 14, 2024 Posted August 14, 2024 This bug has been occurring for quite some time, and I kept thinking it would eventually get fixed, but then I realized maybe no one else is reporting it. When activating a new trackable, I often put "John's" (my name) in front of the existing/default name of the geocoin. I do this in Step 2 of the activation process. (See example screenshot 01). However, once you proceed to the next step, the apostrophe somehow morphs into random characters. (See example screenshot 02). I'm used to the error, so I know I always have to go back and fix it afterward. It can be easily fixed by going into the Edit function of the trackable and changing the random characters back into an apostrophe again. (See example screenshot 03). Once this is (re-)done, the apostrophe shows correctly. (See example screenshot 04). But it never works when done in the original step during activation, only by going back and doing another Edit step afterward. Can this be fixed so that the apostrophe "translates" correctly the first time, during the initial naming/activation step? Many members don't even notice that it happens, and their trackable/geocoin goes out into the world with a bunch of random characters in the middle of its name. Let me know if you need some examples of ones that have been released unnoticed. I've seen a couple just within the past two or three weeks, but it would probably take me a bit to remember where I'd seen them. Hoping the screenshots/explanation will help you to track down the problem. Thanks! 2 Quote
+Nite*Owls Posted August 31, 2024 Posted August 31, 2024 I've seen a few of these too. Definitely should be fixed as it makes the trackable name look garbled. People rarely double-check things to make sure they are good and correct so it doesn't surprise me that this happens. Quote
+cerberus1 Posted August 31, 2024 Posted August 31, 2024 This happens with email as well. You see it as your example one, but the person receiving it sees it "corrected". IIRC, it has to do with another's setup, and it's been a "thing" so long it doesn't seem it can be "fixed"... Quote
+frumiousb Posted December 21, 2024 Posted December 21, 2024 On 8/13/2024 at 9:53 PM, Spacemann Spiff said: This bug has been occurring for quite some time... When activating a new trackable, I often put "John's" (my name) in front of the existing/default name of the geocoin. I do this in Step 2 of the activation process... However, once you proceed to the next step, the apostrophe somehow morphs into [ASCII -ed.] characters. ... [you have to] Edit ... the trackable and [change] the [ASCII] characters back into an apostrophe again... [then] the apostrophe shows correctly. ... never works when done in the original step during activation, only by going back and doing another Edit step afterward... Can this be fixed so that the apostrophe "translates" correctly the first time, during the initial naming/activation step?... I've been noticing and having the same problem for months as well. A trackable called Fred's Xmas '24 instead gets saved with the name Fred's Xmas '24 Then I have to edit and save each such TB again. Annoying enough on a computer; royal PITA on a phone. Waste of time either way. Also, how about giving us the option to activate a bunch of TBs at the same time at geocaching.com/track? 1) secret TB code ___ activation code ___ 2) secret TB code ___ activation code ___ 3) secret TB code ___ activation code ___ 4) secret TB code ___ activation code ___ ... 10) secret TB code ___ activation code ___ and then iterate through them in order. While you're at it, give us the option on that page (checkbox yes/no) to then pre-fill all of those pages with whatever was on the previous page. Often a set of TBs activated the same day has similar content. Right now we can copy-paste from one to the next but just one section at a time and we have to go back and forth between tabs. You'd be saving us a bunch of time. Quote
+frumiousb Posted April 12 Posted April 12 Eight months. Reported eight months ago. This is *still* a problem. When is it going to get fixed? instead of an apostrophe " ' " the trackable gets " ' " Quote
AngryBeesy Posted April 16 Posted April 16 Thank you for reporting this issue. We are working on a fix for it. It happens when you first activate a trackable. As a workaround, if you go back to edit the trackable's title after activating it, the apostrophre will render correctly. Sorry for the inconvenience. 1 1 Quote
+frumiousb Posted April 25 Posted April 25 The ampersand (&) also renders as its reference code. 1 Quote
+Spacemann Spiff Posted May 6 Author Posted May 6 On 4/16/2025 at 11:35 AM, AngryBeesy said: Thank you for reporting this issue. We are working on a fix for it. It happens when you first activate a trackable. As a workaround, if you go back to edit the trackable's title after activating it, the apostrophre will render correctly. Sorry for the inconvenience. It seems the issue has expanded to other areas. I've noticed recently that the reference codes (or whatever they're called) have begun showing up in geocache names as shown in the "Recently Viewed Caches" on the Dashboard, too. See example screenshot. These seem to be corresponding to emoticons rather than specific punctuation marks, but it's still something I don't think I've seen show up this way before. The emoticons display perfectly fine in the next section down on the Dashboard, "Your Logs (Last 30 Days)." Doesn't make sense why they wouldn't display properly in the "Recently Viewed Caches" when they display just fine immediately below that section. Quote
+Viajero Perdido Posted May 6 Posted May 6 (edited) Yes, it seems to be contagious. It's spread to descriptions of images uploaded directly to cache pages too. Edited May 6 by Viajero Perdido 1 Quote
+The A-Team Posted May 7 Posted May 7 3 hours ago, Spacemann Spiff said: It seems the issue has expanded to other areas. I've noticed recently that the reference codes (or whatever they're called) have begun showing up in geocache names as shown in the "Recently Viewed Caches" on the Dashboard, too. See example screenshot. These seem to be corresponding to emoticons rather than specific punctuation marks, but it's still something I don't think I've seen show up this way before. The emoticons display perfectly fine in the next section down on the Dashboard, "Your Logs (Last 30 Days)." Doesn't make sense why they wouldn't display properly in the "Recently Viewed Caches" when they display just fine immediately below that section. Yeah, I believe this is new behaviour. I reported it a few days ago: 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.