W8TTS
-
Posts
367 -
Joined
-
Last visited
Posts posted by W8TTS
-
-
I built a PQ from a bookmark, checked it to run one time and "Uncheck the day of the week after the query runs", which it did. Then, this morning the PQ ran again WITHOUT the day being checked.
-
Thanks for the "New, Fresh Look for the Geocache Details Page" and especially the new large
if you've found this cache. I know at least one cacher that will really benefit from this. -
So, what is the delay with the new cache page? I had it, lost it, had it, lost it. How long is the test going to take?
Me too. And, right now it's gone.
And, I'd really like to see it go live for everyone! 
-
I brought up the same concerns when they announced this in one of the update threads a few months back. If you don't know that you are part of a test and you have no means to give feedback on the experience, what's the point? All it does is confuse people.
I opted in to test the new Google Maps, (for Google, not Geocaching.com), and there is a box that I click to give feedback about missing features or features that are not working as I expect them to. Groundspeak just throws a page out there and waits to see if anyone complains.
I had a bank do that to me with their bill payment application, do beta testing for them without asking, and I'm no longer with that bank. In fact that bank got bought out by another bank. Servers them right.
And, no way to give feed back back to the Frog. It figures, they really don't listen to their members any way. Look at the Challenges they brought out in an attempt to replace Virtuals.
-
Ted, we get that you posted a screen image from the new format for cache pages. What isn't working in that picture? You keep saying "it" (the screen shot) doesn't work. Obviously the screen shot works or you couldn't show it to us. WHAT DOESN'T WORK? Why won't you tell us what you are having a problem with? You are trying to do something (what?) and can't (what happens?) but you haven't told us any details.
Never mind! I was trying to figure out why it WAS working for me but not my friends. And, it's because the powers to be decided to turn it on for me in Chrome as a "tester" without telling me that they did. Poor PR. Also, I was trying to figure out why it wasn't there at all in FF, and it was because of the special cookie that was only in Chrome.
-
What "it" are you referring to? The new cache page design and graphics, or a particular function of the new cache page design. You keep referring to "it", but you're not being very clear about what "it" is.
If by "it", you mean the new design, it is in testing mode and some of us see it while others don't. It has to do with a particular version of a cookie that Groundspeak is setting for your browser. If you see it in one browser and not the other, it's because one has the special cookie and the other doesn't. If you look at the url in the address bars, you will see that they are of a different format. Copy the url from Chrome, (where you see the new design), into Firefox, and you'll see that it works in Firefox as well.
"It" was the screen image that was in my first message. The new design. I guess. I thought it was production.
It would have been nice of them to tell "some of us" that we were part of the testing group. I've been talking to friends about the new design, and they have no idea what I'm talking about. A little heads up from them would have been nice.
-
Why won't the new "Find It" work in Fire Fox?
I'm not quite sure what you mean by "the new 'Find it'". That doesn't match anything in your screenshot. Do you mean the "Log a new visit" dropdown?
Anyway, I'm also getting the new site layout, and I just tried every function in your screenshot, and they all work fine for me with Firefox 22. If something isn't working, I don't think it's the site that's the problem.
It sure looks like my screen shot from the a cache page.
I installed FF 22 (and now have all that Yahoo crap
) and it still doesn't work. I have 2 friends that use FF and it doesn't work for them either. -
Why won't the new "Find It" work in Fire Fox?
It works just fine in Chrome.
And, I can't log in through IE to check it. Where do you see this? I'm not seeing it on the cache listing page.
It's on the cache page in the upper right. As I said it works for me in Chrome, but not in FF (21.0). Looks like I may have to go to 22, and that may cause a problem with my stupid bank.
-
Why won't the new "Find It" work in Fire Fox?
It works just fine in Chrome.
And, I can't log in through IE to check it. -
How do I tell you guys that I really LIKE this?
Yep, and the link to "Logged on" is working
I not only like that, but I also like that it will show a previous DNF as well!
Yep. And, it will probably save me a lot of work with my friend who is NOTORIOUS for double logging finds. He never saw or paid attention to the old "You logged this...", and I told him, if he logs anymore doubles he's going to get his fingers smacked with a ruler.
-
How do I tell you guys that I really LIKE this?
-
Anyone else having newly scheduled PQs not run?
I added some new PQs and scheduled them to run, but they never did. If I make a copy of them, and set them to run, they run right away.
-
One of the options in Create/Edit Geocache Pocket Query is the "Updated in the last 7 days". It would be great if the number of days was selectable in the range of 1 to 7. I know it would cut down the number of PQs that I run.
-
Terms of Use and Privacy Policy updated for all of our websites and mobile applications; we've tried to make them easier to read, and better address legal and privacy issues in the European community
Probably like most users of the site I don't maintain local copies of those two documents so a diff is a bit hard. A few words about the area and what changed would be appreciated.
I'll +1 this. Especially when it comes to the Terms of Use and Privacy Policies.
-
The status page is a joke. It takes a human to tell it that something is wrong. Shouldn't it be the other way around?
Yea. I know. And, it should be the other way around, and could easily be that way. It could even notify someone that there's a problem. What a concept.
-
Yep, same here. Trying to work through the GSAK API interface. Nothing is working. Getting a new Token looks like it work, but then it crashes.
Looks like the frog fell off his Lilly pad and doesn't know it. The Geocaching System Status is reporting everything as "Healthy".
-
The "nano" cache size was discussed a long time ago, and according to what was said back then it was in the works. But, when they changed the forum style it appeared to drop into the Lilly pond. It's something that has been needed for a long time. So, this gets a +1 from me.
-
It's working fine now.
-
Trying to down load PQs using the API this morning? It appears that the API server isn't responding. I can access the PQ's that were run using the PQ pages, but not the APIs.
-
On the Geocaching > Your Pocket Queries > Create/Edit Geocache Pocket Query screen, one of the option in the "That (And)" is "Updated in the last 7 days". It would be a useful upgrade to PQ's if we could select:
Updated in the last day, or
Updated in the last 2 days, or
Updated in the last 3 days, or
.
.
Updated in the last 6 days, or
Updated in the last 7 days
It could cut down on the size of the PQ's, they would probably run quicker, and more could be emailed.
Just a thought.
-
It's time that the NANO is added to size.
-
And, if there were such a warning/alert/message, you would only see it if you were logging your find from the cache page.
Granted that such a warning would possibly catch a generous percentage of mistaken multiple logs, there will still be a significant number of multiple logs.
Those who care about their stats will learn from their mistakes and be more careful in the future.
Those who don't are possibly destined to go on finding the same caches time and again.
And, when you hit 20K, as this guys about to, and are old, and not computer literate, finds become a blur and the more help you have in not making a mistake the better you like the game.
-
And you'll only see that if you visit the cache page. If you're logging via field notes, smartphone, or GSAK, there's no need to visit the cache page at all.
I'll +10 this. There are constantly cachers coming to the forums asking why their stat line has a difference between the number of finds and distinct caches. It's a de facto standard that you only log a cache as found once. Some people choose to log caches more than once, and that's fine. However, for the vast majority, logging it as found a second time is an error for which there's currently no alert. This feature would be a minor inconvenience for a small segment of the community (those who multi-find), but it would be a significant improvement for the majority.
And, if your logging in GSAK and using the API interface, and try to log a dup you get a message saying that you are trying to. Thanks for the +10!
-
I have a friend that isn't too careful with his logging. He'll go to an area and find caches, then a year or two later go back to that same area, find caches that he's already found, not remember that he's found it, and log a second find. Some times they get caught, sometimes they don't.
Why doesn't Groundspeak, when someone goes to log a second find on a cache, pop-up a message asking if the cacher is sure he wants to log a second find. Something like "You have already logged a find on this cache on March 4, 2007. Are you sure that you want to log another find." and have a Yes and No button.
I know that there are caches that allow double find logs, but 99.9% don't. Something like this would help solve a problem that some people have.
And, yes I know that when you bring up a cache to enter a log it will tell you when and if you've already logged a find. But, it doesn't stand out enough.
if you've found this cache. I know at least one cacher that will really benefit from this.
And, I'd really like to see it go live for everyone! 
Pocket Query problem
in Website
Posted
The reason that you didn't see it is, I deleted it right after it ran the 2nd time. But, like JHolly said, it appears that happens when the day is checked in the actual "Pocket Query" page and not the "Your Pocket Queries" page.