Jump to content

What happened to the Signal emoticons?


steben6

Recommended Posts

Up until the last few days, you could put the Signal emoticons (as displayed in the forums) in a log for a cache or trackable by using the same tag. For example: ":tongue:" would give you that emoticon. Now, those emoticons have been red-X'd out in all my logs. Since I have Signal in about a gazillion logs, I was wondering what happened? :sad:

Link to comment

Up until the last few days, you could put the Signal emoticons (as displayed in the forums) in a log for a cache or trackable by using the same tag. For example: ":tongue:" would give you that emoticon. Now, those emoticons have been red-X'd out in all my logs. Since I have Signal in about a gazillion logs, I was wondering what happened? :sad:

 

This has been reported by quite a few people. I wish you all luck in getting it restored as it seems that it was an undocumented feature. I would guess that most of us didn't even know that you could use those emoticons in a cache log.

 

It's really a shame that so many people's logs are now broken.

Link to comment

Not only are these broken images in my logs - but they're also on my cache pages. :angry:

Still no progress on fixing this. I'll offer, once again, to assist in the squashing of these bugs. Groundspeak! Drop me a line. We'll do lunch. :grin:

 

Fixing this? They haven't acknowledged that anything is broken. It's really sad, but they have completely ignored this.

Link to comment

Check out the "GSAK & NUVI issue" topic in this forum. This maybe the reason.

I don't think it is related. The "signal" icons are like the normal ones - they use plain ASCII substitutions:
Signal:  Normal: []

The problem is that Groundspeak physically removed the icons from http://img.Groundspeak.com/forums/emoticons/signal/smile.gif

 

It was enlightening to check out the root of the image repository: http://img.Groundspeak.com/ That's very ugly for a public page.

 

It would appear they ran a "handler" that physically migrated images to a new location. They did NOT update the substitution variables to the new URL for the images. Perhaps they deleted the images by accident? Perhaps they forgot about them? Perhaps they have banished Signal for freebasing wart-cream? We'll never know. :sad:

Link to comment

Still no fix. :sad:

Broken images still persist in nearly every one of my previous logs. Because I'm an optimist I continue to use the :smile: codes.

Will you post an example? I looked at some of the OP's logs and some of yours, and can't find broken [x] images. I see smilies. They aren't frogs, they're smilies. Is that the issue?

Edited by kunarion
Link to comment

I see frog faces just fine. I guess that it is fixed or is it browser dependent.

 

Are you talking about the forums? :lostsignal: The trouble seems to be happening with logging a find on the computer.

Yes, sorry. I was referring to the forum only, thought it was sourced from the same place.
Link to comment

check this links

 

<img alt="" height="19" src="/images/icons/bad_boy_a.gif" title="" width="19" />

<img alt="" height="19" src="/images/icons/tongue.gif" title="" width="19" />

<img alt="" height="19" src="/images/icons/cute.gif" title="" width="19" />

<img alt="" height="19" src="/images/icons/smile.gif" title="" width="19" />

<img alt="" height="19" src="/images/icons/surprise.gif" title="" width="19" />

<img alt="" height="19" src="/images/icons/tired.gif" title="" width="19" />

Link to comment

That’s one more post for me! Thanks so much for creating this thread. :laughing:

 

As an FYI - you might not see the broken images depending on your web-browser and definitely wont see them when viewing them through The App. For the past year or so I've duplicated all of my :smiles: with a [: )]

 

A bug on this was added to our backlog back in May. It has simply not been prioritized into the development schedule.

Good to hear! I'll continue to be (somewhat) patient and occasionally monitoring this thread. :anibad:
Link to comment

Been a while since I bumped this. This will be the last time.

With the most recent changes to the logs the Signal Icon Shortcodes were generating broken images in all browsers instead of just IE. Soon thereafter I noticed the shortcodes were no longer parsing at all. :angry: Since GC.com has demonstrated that they really don't care if the logs look like unshaved donkey I plan to continue my anachronistic use of the shortcodes. I might even start adding useless BBcodes too. Hooray for backwards compatibility! :laughing:

 

With this issue "resolved" they can start focusing on allowing us to use HTTPS links in the "Related Web Page" and fixing it so App-Only users aren't invisible on the website in "last visit" or premium cache audit logs. :anitongue:

Link to comment

Ok, I'm bumping it again just because I was informed today via the weekly newsletter that the Signal Icons are back for the forum. I wasn't aware they left. :cool:

Reading back I see they've managed to fix a few things such as the "Related Web Page" issue... by completely removing the option. Success! :bad:

Joking aside, there has been quite a bit of development over the past two years and most of it really is for the better... or at least compliant-with-modern-technology. :grin:

Next up - iframes and audit logs? 

Link to comment
On 2/22/2016 at 10:20 AM, cerberus1 said:

Kinda surprised that Groundspeak still continues to keep it, as it hasn't been accurate for some time. :)

It's 100% accurate at doing what it says it's doing, providing a  " list of users who have viewed your premium member-only cache on the web site", with number of times, date of first and last visit. 

Link to comment
2 hours ago, Isonzo Karst said:

It's 100% accurate at doing what it says it's doing, providing a  " list of users who have viewed your premium member-only cache on the web site", with number of times, date of first and last visit. 

Curious, and haven't bothered to play in a while, but are you saying that bookmarks and PQs no longer bypass the audit?

 - if the only time a user is shown on the cache page is when finally logging a find, is it accurate?   Thanks.  :)

Edited by cerberus1
to add...
Link to comment
Quote

if the only time a user is shown on the cache page is when finally logging a find, is it accurate?   Thanks.  :)

 

This new "feature" (loading the cache page after a log entry is completed) has impacted my bypass-the-audit-log procedure.  

Now I have to log through the app, then go back to edit the date (because you can't set a log date in the app, as far as I can tell)

I'd be happy to see the audit log go one way or another.   Eliminate it, or make API call visits get logged as well.  

Link to comment

A user shows up on the audit log if they look at the cache webpage on Geocaching.com. You can bookmark, PQ and log a find without doing that. I'd say in the phone caching era, it's common to hunt and find caches and never see Geocaching.com.  

15 hours ago, frinklabs said:

This new "feature" (loading the cache page after a log entry is completed) has impacted my bypass-the-audit-log procedure.  

?? is this "new logging", or a phone app feature?  I don't think I've ever logged from a phone - I have cached from a phone, but I log from a computer.   I've opted out of "new logging" (though I just discovered that if I load drafts to the site, that opens the New logging page). I

It's possible create a PQ that includes a cache, or  Bookmark, or to hunt and log a cache without ever loading the cache page on Geocaching.com. 

Edited by Isonzo Karst
Link to comment

It is the new logging. 

For awhile I was non-PMO so I didn't know that website was dropping you to the cache page, post-log, until Santa got me a PMO and I found out the hard way.

It is mos def possible to bypass the audit log altogether, but it is more of a process than it was before.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...