HiddenGnome
-
Posts
162 -
Joined
-
Last visited
Posts posted by HiddenGnome
-
-
Quick update: the 500 error for the Mystery at the Museum souvenirs has been resolved. Click away!
- 1
-
16 minutes ago, fizzymagic said:
Web-based map is broken. Shows the filtered caches on the left-hand list but they do not all appear on the map.
How about a "small update" to fix this rather large problem?
Sorry about the snark. It's just that I have lived through so many years of Groundspeak not implementing features that we begged for that it is particularly galling to see so much wasted effort on a promotion that doesn't even work properly.
I am sorry that you are missing data on your map. Can you provide more details about what you are seeing? What filters are you using to search and what area are you searching in?
- 2
-
- Popular Post
- Popular Post
7 hours ago, MartyBartfast said:I completely agree, and it happens time and again with new features, it seems like the customers ARE the testers.
I wonder if there's scope for a new breed of community volunteer, we already have reviewers & translators, perhaps they could recruit volunteer testers and test this stuff out on the staging site. I think there enough people in the community with various levels of software/design/infrastructure experience who would be prepared to poke & prod new releases for them.
I acknowledge that there were issues during the launch of this promotion and I take responsibility for that. I don't like that members of the community have to deal with bugs and come across situations that were not anticipated. This promotion is both the most complex and most tested promotion we have ever launched. Yes, there were bugs. However, I can assure you that there are a lot fewer bugs then before we had 20 people hammering on the system for 2 days. We are continuing to evaluate how we work and how we can improve. Sometimes the changes we make aren't felt directly by the community, but we are continuing to make improvements none-the-less.
I am not going to make excuses for releasing code that has bugs, but we also cannot always cover every single permutation that might arise. What I will promise is that we will try to catch as many bugs as possible before a release and then fix the bugs that do make it to the community quickly. We are a small team and are moving quickly to address issues. I apologize for inconveniences that anyone has experienced and I thank you for your patience.
- 6
- 1
- 5
-
1 minute ago, Max and 99 said:
Drats! I was hoping my new cache would have a clue!
All new caches will have a clue. Sometime today the system will begin picking up new caches automatically. If your cache is published before then it might not have a clue for up to an hour, but I am regularly running a script to add clues to new caches. I am also keeping an eye on this thread in case there is a cache that doesn't have a clue.
- 2
- 1
-
8 hours ago, Doudou_72 said:
Still an "Error 500" when trying to watch the "Briefed on the case" Detective Souvenir in the website. Is that normal ?
We have fixed that issue, but have not deployed it yet. It will be updated soon.
- 1
- 1
-
7 hours ago, bruzie said:
A new (virtual) cache that was published today at 2019-07-12 0000 UTC doesn't have the Detective clue. With your use of tense here, does that mean it won't get the clue? (GC89178)
4 hours ago, Tungstène said:GC89ZXC and GC8A72F were published today by a friend of mine but none has a clue. Is it expected behaviour, @HiddenGnome
?If the geocache was created before this week then it is expected to not have a Clue when it is published. We are working on a small update to automatically add a Clue whenever a geocache is published which should be ready soon. Until then I am running a script that will retroactively add the Clue to recently published geocaches.
- 2
-
- Popular Post
- Popular Post
I mentioned earlier that I would provide additional background into the issue people reported about not collecting their Clues. This issue was initially difficult to troubleshoot because it was not the result of an error per se - in fact, as far as the system was concerned it was behaving correctly.
Some quick background - in order to complete the Mystery at the Museum you need to collect a variety of Clues. Each Clue has unique attributes associated with it, i.e. number of finds required, level required to unlock, and activation date. Every Clue has an activation date of today at 12 (noon) UTC.
When a geocache is logged the system compares the date of the log with the activation date of the Clue to make sure it falls within the allowable window. However, because of an issue with how dates are formatted from the website when they are converted to UTC there were a number of instances where the log date was interpreted as being before noon UTC. According to the system those logs did not fall within the allowable window and so were ignored. Logging from the app did not have this issue because the dates were not experiencing the same formatting issue.
Once we realized this was happening we made a couple of small modifications that would resolve the issue and deployed them to our servers. Once deployed I saw (so I thought) the data that we were expecting and announced that the issues was resolved. What I did not realize was that although the issue had been correctly identified and a fix applied the servers did not get properly reset and so did not pick up the necessary changes. That was my mistake, both on not properly resetting the servers and for relaying that the issue had been fixed prematurely. When we realized that the servers had not picked up the changes it was a simple fix at that point to force the update and triple check the data was returning correctly.
- 2
- 6
- 2
-
1 minute ago, arminus said:
great, re-logging yields the souvenir, but clicking on it (https://www.geocaching.com/souvenir/?guid=e234c8a2-191d-4727-81aa-41fd61405daf)
gives my a 500...
I am glad that you were able to successfully collect your clue and that you received your souvenir. We are currently investigating why the souvenirs from this promotion are delivering an error when they are clicked. The fact that the souvenir is being displayed on your profile page means that it was properly awarded and once we sort out the error you will be able to view it fully.
- 1
-
53 minutes ago, arminus said:
can't confirm this: https://www.geocaching.com/geocache/GC88KZ2
Published today, should have an inspector clue according to the blog entry ("New geocaches published between July 11 and August 11, 2019 will all receive the detective clue.")
just deleted the log and re-logged it (Firefox on the website) - still no clue
deleted again, tried to log through the app, can't log a found since the app thinks I already found it
re-logged it on the website (and generated some spam for the watchers I guess...) - again no clue
Hi @arminus - geocaches that were created earlier this week and published today are not currently receiving a Clue which includes the geocache that you mentioned. We are currently working to update the system to make sure that Clues are correctly distributed going forward. Geocaches that were recently published have had a Clue added retroactively. Now that the geocache includes a clue you will need to re-log the geocache in order to receive your Clue.
- 2
-
Hello everyone!
For those of you who have been having trouble collecting Clues when logging a geocache I sincerely apologize. The issue should now be resolved. The fastest way to get your clue will be to (once again) delete your log and re-post it. I will follow-up with a further explanation shortly.
If you continue to have issues please include the GC code or a link to the log, if possible.
Thanks!
- 1
-
2 minutes ago, Max and 99 said:
I did another search, to caches that I have not found, that do have the detective clue, and got a list. When I click on the cache page, it does NOT have the Detective Clue, just the generic message that you need to find clues to proceed.
Hello - would you mind sharing which geocache you are looking at? Thanks!
-
41 minutes ago, Viajero Perdido said:
PS, at the top of the event page, why is time not right beside (or underneath) date? Conceptually, they belong together, no?
Placing the event date on the same line as the time was initially presented by the team. However, the current layout was chosen because it maintains a consistent layout with non-event caches. During this transition period there are still events with no time selected and the layout was confusing when the date was on a separate line without the time.
-
6 minutes ago, Harry Dolphin said:
My souvenir still is dated 12/10/2018. Should be 07/03/2004.
Once the souvenir is awarded the background process that is currently running will not update the "award" date to the earliest log date.
-
1 minute ago, Max and 99 said:
I don't know about "official" but here's the link from another souvenir thread:
https://www.geocaching.com/help/index.php?pg=kb.chapter&id=29&pgid=792#countrysouvenirs
Thank you! I will put in a request to have that list of souvenirs updated.
-
1 minute ago, NYPaddleCacher said:
Although it's not the "official" souvenirs list, the A-Team souvenirs page (https://thea-team.net/souvenir) is generally very up-to-date (though they haven't yet added the 5 most recent souvenirs).
Would you mind pointing me to the "official" list that you are referring to?
-
I apologize for the time that it has taken to get everyone's USA souvenir awarded. We ran into some technical issues that we haven't run into with other souvenirs because of the large number of souvenirs that needed to be awarded this time around. It took a few iterations to update the background process, but we are very close to having all of the souvenirs awarded.
- 2
-
Souvenirs are being retroactively awarded at this moment. USA is going to take awhile ?
- 1
-
Hello - this ratings widget is part of a test in a limited number of locations and has been running for the last couple of months. There is no connection between this test and the GCVote website.
- 2
-
@Funky_Boris - Thank you for bring this up because it could be more clear. The email that you are receiving is a copy of your own message. This happens if you have selected the option in Message Center to "forward messages to email" (see attached). When that feature was added we re-used the existing email template which is causing your username to be added twice because you are both the sender and the receiver of the email.
"Geocaching: {receiving_username}, you have a new message from {sending_username}!"
- 1
-
Hi @kpub66 - I'm sorry this took a while to get resolved, but the issue you were experiencing should be cleared up now. You should be able to access your Statistics once again.
-
I was recently in the Yorkshire area for the UK Mega and was introduced to the circular walks (and the public footpaths) for the first time. There were multiple series that were created around the Ripon and Harrogate areas that I had the opportunity to experience. I have fallen in love with them, but sadly it is not something that seems to have transferred to the US. During my adventures I came across a List that someone created. The geocaches on the list are the first cache in each series with a description about where it is located. Hopefully some of these are nearby!
https://www.geocaching.com/bookmarks/view.aspx?guid=09597bd2-59c4-47be-90a4-f4914cb7043b
- 1
-
13 hours ago, Scarch said:
Sometime after Feb, text notifications resumed, and I have received consistently.
beginning today, text alerts have stopped. About 10 caches have published with no alert text.
hoping this can be revisited.
any others having the same issue
iOS and ATT
Hello @Scarch - I am sorry to hear that you are not receiving your text notifications. These are an important aspect of the game and I can appreciate your frustration. I checked our logs and I can see that in the last 36 hours 11 cache published notifications have been sent successfully to your secondary email address. Unfortunately, we are aware through similar reports in the past that text notifications through ATTs service are sometimes unreliable despite a successful sent message on our end.
-
1 hour ago, Lightning11 said:
All I want is to pay for Premium. The form will not allow me to enter the credit card #.
If you are trying to purchase a Premium membership you should try on this page:
https://payments.geocaching.com
The Help Center is about answering questions and does not provide a way to take credit card information. Hopefully that helps!
- 1
-
1 minute ago, Lightning11 said:
Nope! Still requires CAPTCHA solve and there is no CAPTCHA TO SOLVE.
Hi @Lightning11 can you add a screenshot or an explanation of where you are seeing this issue?
The biggest jewel heist in history!
in General geocaching topics
Posted
Hello! I wanted to drop in and give an update on what we have been working on.