Jump to content

Search the Community

Showing results for 'email SMS'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Geocaching HQ communications
    • Geocaching HQ communications
  • General geocaching discussions
    • How do I...?
    • General geocaching topics
    • Trackables
    • Geocache types and additional GPS-based gameplay
  • Adventure Lab® Discussions
    • Playing Adventures
    • Creating Adventures
  • Community
    • Geocaching Discussions by Country
  • Bug reports and feature discussions
    • Website
    • Official Geocaching® apps
    • Authorized Developer applications (API)
  • Geocaching and...
    • GPS technology and devices

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location

  1. That genie isn't going back in the bottle. I think apps are very useful, but as an entry into the hobby instead of just a tool they do sometimes lead to problems. Verified accounts are a must. If your account doesn't have a verified email should be no logging. Newcomers should get a welcome email with links to intro videos and FAQs. If someone fails to use those resources then coming to grief is on them.
  2. As the majority of mystery caches are not at the coordinates (or those I have experienced), maybe standard text could appear automatically under Geocache Description saying, 'Cache is not at these coordinates', unless the CO ticks a box for, 'Cache is at these coordinates'. That would also cover all past mysteries. An email should be sent out to all COs with mystery caches warning them. Active COs would be able to go in and tick this box if applicable. Any mystery caches (at coordinates) not corrected, it would indicate an inactive CO. The reviewer might be able to pick this up (DNFs, NM), and after a warning, considered whether to archive that cache or not.
  3. I just deleted my MMS email from my geocaching profile. I set it up again and sent verification email to it and it set off my MMS text alert on my phone. So now I wait until a new cache or event publishes to see if it triggers my phone alert.
  4. How many logs you have tagged to helpful or great story? I follow logs of my caches from email. Tagging those logs is out of question.
  5. Following my post above giving feedback on your progress so far, I was happy to wait patiently until you got around to fixing the remaining problems. That is to say, The list will not print text box information The list TITLE text box (that is to say the text box under the title on the list page) STILL does not recognise line breaks and appears as one line of text. Amending a list takes you back to the top of the page (annoyingly) The word wrap on an ordinary list entry is not recognised and text falls off the right hand side of the page. However. today I received a promotional email from you pointing to the official blog: https://www.geocaching.com/blog/2024/04/our-favorite-premium-features-lists/ extolling the virtues of lists as one of your "favourite premium features" to use your own words. This leads me to believe that you think you have solved all the problems listed above which remain. Let me assure you, you have NOT. These four issues remain to be addressed and it would also be good if you could give us some indication that you are aware that the problem still exists. Starting to feel pretty frustrated by now.
  6. I recommend contacting the EarthCache reviewer for your area, GeoawareUSA10, by email through his profile page. GeoawareUSA10 covers all the states near your home (PA, OH, KY, WV, MD, NY, etc.). If your ideas come from more distant travels, let us know where. If you stray much further south (Virginia, Tennessee, etc.) you would switch over to geoawareUSA9. Both of them have handy maps on their profile page to show how coverage for the USA is split up. Many Reviewers, including myself, do not use the message center for "official business," but others do. It's always a safe bet to start your contact with an email through Geocaching.com, and then ask later if the message center is OK. Don't be surprised if you're asked to write up a draft cache page with all the details. Email is fine for general questions, but at some point the geoaware will want to see the exact text for the background information and verification activities/questions.
  7. I'm sorry if this has been asked before or not, but is there a way to contact Geoaware? Do the accounts have a generic email address that they all use? Or should I contact them through individual accounts? Do they check messages when you send them a message through the message system? I am trying to get a couple ECs together, but I would like get some guidance from them before I proceed much further with these ideas. Any help would be appreciated. Thanks!
  8. I recently stopped receiving email notifications for my owned caches ,and new publications and watchlists .. I have checked my spam and they are not there .. how do I fix this problem?
  9. Nochmals danke für die Info Meine letzte Frage wie kann ich Groundspeak kontaktieren Welche Email Adresse Mit freundlichen Grüßen Brinnel1500
  10. I was so excited to see this in my email this morning - finally my big backlog of waymarks is cleared! Nope - it's twenty approvals for the same waymark. The server must have had the hiccups this morning.
  11. Geocoins for sale, all unactivated. No fee paypal is the preferred payment method. Price beside each is for the coin, it'll be about $3 more for tracked shipping, so add $3 onto the cost of the first coin you select. Any additional coins do not incur any added shipping charge. First picture: first row: Cystic Fibrosis breath of life ($10) Yemon Yime breast cancer coin with pouch $14) Yemon Yime breast cancer coin without pouch ($12) Team S&B breast cancer coin ($12) Love coin with purple translucent insets ($12) second row: Flip-a-phone pink glitter ($14) Going Ape coin that was only available as one per person at a GW ($18) Not another micro ($12) Caching it's in the blood ($12) Midnight FTF cachers ($12) third row: Vanelle Marvelous Nature LE ($18) Black rose 2011 coin ($18) Big blue switch 10 years of geocaching ($10) Brian from HQ personal gnome trackable ($10) Carnival geocoin with embedded beads ($14) Turn every location into an adventure big blue switch ($10) fourth row: 9/11 ten year anniversary we shall never forget ($10) dry creek geocachers geocoin (3 available) ($9) Cachers for the cure breast cancer geocoin, one gold, one black and one silver ($12 each) fifth row: going APE trackable ($8) Geotriad coin ($12) Going APE small coin ($10) APE trackable ($8) Second photo: Kathy's coin two Heaven's the place geocoin with proxy ($18) Snag the Tag high and low coin set ($20) Either post a reply here or feel free to send me an email thru the geocaching website.
  12. That's what I recently had to fix with Kit and the Wherigo Foundation site. PKCE (proof key code exchange) is a way to make it more difficult for someone to intercept your login. The app will have to send something in addition to what it usually sends, then validate against it. It seems Groundspeak sent information out to all API developers about a year ago for this. I didn't "get the memo", so to speak, because I had changed my email address and never alerted someone at Groundspeak. @spstanley, are you still handling the iOS player app? PKCE is covered in the API documentation.
  13. I have sent an email but no updates back yet on login info.
  14. It seems partners@ was the wrong address. It also looks like I hadn't updated my partner email address with Groundspeak, so the email went to the email address I discontinued using and checking a couple years ago. All praise be to Annie, who kindly sent that email address a copy of the email, so it was sitting at the top of the mountain of spam (even email addresses you only use with geocachers aren't safe when someone's account is exposed). You can log into Kit now. I'll update the WF site after this. I keep thinking about updating one or the other. Updating Kit would be fine. Updating the WF site and trying to extend Wherigo's capabilities is overstepping it without getting Groundspeak behind it again (so it's not a wasted effort), and I'm not going to ask until I have commitment from a community team and a plan in place. It's not a one-person show.
  15. We are aware that some geocachers using API partner applications are running into an error during the authorization process since our last update. HQ has been providing notice to API partners for several months to update their authorization process ahead of an update that was implemented last week. It is very likely that users' inability to login to Wherigo Foundation results from the necessary update not being completed on the WF side. If you're having trouble updating on the WF side, then please contact HQ's API team. (We have not received contact from you via the partner email address as of today.)
  16. I am not having email problems, just the notifications for newly published caches that I receive in text message form. I don’t remember exactly when they stopped coming through, but it was around early February. There are several other geocachers in Central Florida having the same problem. We all have AT&T as carrier. I do receive the texts when I am sent a GC Message, so that format is coming through my carrier just fine. I don’t know how widespread this is, but I believe its not a phone problem. i have created new notifications to test if there might have been a procedural or format change that effected the notifications that were in place at the time a change may have been made, but newly created ones do not work either. AT&T said they would need to know more about the sent message in order to track or trap or identify if it’s even getting there. The tech suggested the originating party should contact their carrier and initiate the analysis, so the routing can be determined and likely a resolution will be found. I fully agree with that suggestion, but I don’t know how to get this message into the hands of someone at headquarters that can actually put this process into action.
  17. No, it's likely something on Groundspeak's side with transferring the login back to Kit and the WF site. I sent an email outside work hours on Friday. They'll look into it during the work week. If I don't hear anything by Wednesday, I'll send an email to another address I know. This happened around the time I renewed the site's SSL certificate, but is not related to it. I updated the SSL certificate on Wednesday. That evening, my hosting provider had problems making the database accessible to the web server. I thought it was something I had done, but I couldn't figure out what, so I left it unsolved overnight. On Thursday morning, the database connection was working fine and I was able to log in. This new problem seemed to have happened between Thursday afternoon and Friday afternoon.
  18. There was indeed something wrong with your email address(es) and the PQ form was not seeing a validated email address for your account for some reason. I was able to fix the issue by adding your existing email to your account again and validating it. Your account now shows that single, validated address and the PQ form is filling in properly with it.
  19. Ok, I research a bit and now I remember what the problem was. My email was not verified but could @Moun10Bike soved it: Sine I delete my 2nd email address (few days ago) it appears again, so may my first is again not verified? (I receive mails for logs, notifications, PQs, etc anyways). So I would assume that the bug is in the email verification.
  20. This bug appear since serval years and it was reported multiple times. I thought a while that it has been fixed, but it hasn't. Since I remove my second email address, the bug appears again. So I would assume, that the error is caused by the broken email input on PQs and notifications. (If you only has one email address) It is a really annoying bug, but i gave up to hope that it will be fixed : ( Error 500 normally means "Internal Server Error", so the clients system doesn't matter. It is an error on server side whitch should never happen in a production release.
  21. I miss the days when the weekly email actually had personalized information, and actually listed new caches and upcoming events near your home coordinates.
  22. Proximity search sorted by newest first. Results - dynamic, email text - static. 'New' could mean caches you haven't looked at yet. Could be in an area with nothing published in the last 6 months. So much variance in the results and local region that I wouldn't take "new caches" literally true in a single inferred sense for every person who gets the newsletters But, it would be more consistent and true if it were worded something like "Latest caches" or "Most recent published caches" instead of "new"
  23. Did you look at the Geocaching Regional Placement WIKI for Montana ? Much info online is from 2004-2009, so most probably not good anymore. Wherever you hide, you need to ask for permission anyway, so a simple call or email to where you had in mind is a good start.
  24. From the Help Center: You can temporarily disable your cache page if the cache needs repairs or if the area is closed temporarily. (The cache does not need to be missing to be listed as disabled) You can make a list of "Caches I need to check on", but that could be forgotten just as easily as the information in a notification email. Disabling the cache gets more notice.
  25. So, I can upload drafts Using Cachly, I can then post those drafts after editing, I can look at something called the Cache Owner Dashboard but all that lets me do is look at recent logs on my caches which I already read in my email. Now, I want to look at my Friends list ... nope, no link on the useless dashboard. My statistics? Nope no like on the useless dashboard. It has lots of nice white space for no apparent reason. Guess I'm done with geocaching for today. Maybe someone in Seattle will fix it tomorrow morning. One can only hope.
×
×
  • Create New...