Jump to content

New maps

team tisri

By team tisri
in Website

Followers 1

Recommended Posts

mellers

+mellers

Posted
Posted

Yes - it's happened both on my laptop and my main PC. On the main PC, it had an additional sentence of "do not allow this page to generate dialogue boxes again" or some such command, so I clicked the button next to it and OK and it hasn't come back. I've noticed that it only seems to appear when I have the geocaching map up. Maybe that's just coincidence though.

missionMode

+missionMode

Posted
Posted

I was worried I got a virus or something, and then thought perhaps I had mistakenly created a calendar event in google that was called yes, but just now realized it was on the map. I am guessing this is somebody's debug information left behind.

jri

jri

Posted
Posted

I've not had this issue myself, but someone asked if it might be caused by one of my Greasemonkey scripts, so I did some poking around. It looks like it's being caused by geocaching.com itself, and is some time-related code triggered by leap years, which explains why it's just started today.

 

Since code comes from geocaching.com, there's not an easy way of avoiding it. On some browsers the "yes" alert may come with a tick box that you can use to stop further alerts, but this will only work until you re-load the page or Groundspeak fix the code properly (which should be trivial!).

 

For the nerdy, the main maps page downloads a utility script (with a really long address starting http://www.geocaching.com/ScriptResource.axd?d= followed by a string of random characters). This includes a DateTime module containing the offending function:

 

DateTime.isLeapYear = function (year) {
   if (((year % 4 == 0) && (year % 100 != 0)) || (year % 400 == 0)) {
       alert("yes");
       return true;
   }
   return false;
};

Basically, every time this function runs during a leap year, it pops up "Yes" - it looks like a leftover bit of debugging code. From what I can guess, this will happen every ten minutes, but only for Premium Members (which may be why I've not seen the problem).

 

That's my guess at the explanation, hopefully there will be a fix along soon...

 

JRI

terrkan78

+terrkan78

Posted
Posted

I've not had this issue myself, but someone asked if it might be caused by one of my Greasemonkey scripts, so I did some poking around. It looks like it's being caused by geocaching.com itself, and is some time-related code triggered by leap years, which explains why it's just started today.

 

Since code comes from geocaching.com, there's not an easy way of avoiding it. On some browsers the "yes" alert may come with a tick box that you can use to stop further alerts, but this will only work until you re-load the page or Groundspeak fix the code properly (which should be trivial!).

 

For the nerdy, the main maps page downloads a utility script (with a really long address starting http://www.geocaching.com/ScriptResource.axd?d= followed by a string of random characters). This includes a DateTime module containing the offending function:

 

DateTime.isLeapYear = function (year) {
   if (((year % 4 == 0) && (year % 100 != 0)) || (year % 400 == 0)) {
       alert("yes");
       return true;
   }
   return false;
};

Basically, every time this function runs during a leap year, it pops up "Yes" - it looks like a leftover bit of debugging code. From what I can guess, this will happen every ten minutes, but only for Premium Members (which may be why I've not seen the problem).

 

That's my guess at the explanation, hopefully there will be a fix along soon...

 

JRI

 

Thanks for the explanation. I wondered why I was getting "yessed." :)

power69

+power69

Posted
Posted
From what I can guess, this will happen every ten minutes, but only for Premium Members (which may be why I've not seen the problem).

 

That's my guess at the explanation, hopefully there will be a fix along soon...

 

JRI

10 minutes? not here. clicking a cache icon on the map brings it up 30 secs later. this is reproducable

Chrysalides

+Chrysalides

Posted
Posted

Running chrome for today (using wife's laptop) and got that message, coincidentally right after I sent in an answer for a virtual. For a while, thought "cool, instant notification for virtual answers!" before thinking nah and figured it had something to do with debugging, especially since this is a new year. Didn't think it's leap year related though, thanks for the enlightenment :)

jholly

jholly

Posted
Posted 

DateTime.isLeapYear = function (year) {
   if (((year % 4 == 0) && (year % 100 != 0)) || (year % 400 == 0)) {
       alert("yes");
       return true;
   }
   return false;
};

 

Well I'm glad to see they can figure out if it is leap year or not.

unclehappy

+unclehappy

Posted
Posted

Try this out. I live in Reno,NV. and we had two caches published around 4:50pm today. I looked at both descriptions on maps then opened other windows for other things. After about 20 min. I got a "yes" window then a minute later got another, one of the caches had two found it logs posted. A while later another "yes",one of the cachers logged a DNF at the other new cache.?

 

Although now I've waited to post this thought and it seems it was just good timing,every 10 min. And yes I'm premium mem.

 

How 'bout it Groundspeak? Got my ear to the rail.

 

Hope I don't have to wait four years for a fix!

gpguyway

+gpguyway

Posted
Posted

Yes - it's happened both on my laptop and my main PC. On the main PC, it had an additional sentence of "do not allow this page to generate dialogue boxes again" or some such command, so I clicked the button next to it and OK and it hasn't come back. I've noticed that it only seems to appear when I have the geocaching map up. Maybe that's just coincidence though.

 

I have been getting the same thing on my screen.

gpguyway

+gpguyway

Posted
Posted

I've not had this issue myself, but someone asked if it might be caused by one of my Greasemonkey scripts, so I did some poking around. It looks like it's being caused by geocaching.com itself, and is some time-related code triggered by leap years, which explains why it's just started today.

 

Since code comes from geocaching.com, there's not an easy way of avoiding it. On some browsers the "yes" alert may come with a tick box that you can use to stop further alerts, but this will only work until you re-load the page or Groundspeak fix the code properly (which should be trivial!).

 

For the nerdy, the main maps page downloads a utility script (with a really long address starting http://www.geocaching.com/ScriptResource.axd?d= followed by a string of random characters). This includes a DateTime module containing the offending function:

 

DateTime.isLeapYear = function (year) {
   if (((year % 4 == 0) && (year % 100 != 0)) || (year % 400 == 0)) {
       alert("yes");
       return true;
   }
   return false;
};

Basically, every time this function runs during a leap year, it pops up "Yes" - it looks like a leftover bit of debugging code. From what I can guess, this will happen every ten minutes, but only for Premium Members (which may be why I've not seen the problem).

 

That's my guess at the explanation, hopefully there will be a fix along soon...

 

JRI

 

I like you explanation the best but if it is going to last all year for premium members maybe I should not renew on Jan 3 as I am suppose to and all other premium members should not renew the subscription and that might get the programmers working a little faster on fixing this problem.

jellis

+jellis

Posted
Posted

but what is getting annoying now is when I have the maps open on a tab and I am doing something else on another tab, the message sends me back to the map "yes" tab suddenly when the message shows up.

luvvinbird

+luvvinbird

Posted
Posted

It happened twice to me yesterday. While creating my log to submit, right in the middle of it the map page appeared along with that "yes" pop-up. It completely wiped out my logs and I had to start over. Hopefully, an update from GS will fix this bug.

NYPaddleCacher

+NYPaddleCacher

Posted
Posted

I've not had this issue myself, but someone asked if it might be caused by one of my Greasemonkey scripts, so I did some poking around. It looks like it's being caused by geocaching.com itself, and is some time-related code triggered by leap years, which explains why it's just started today.

 

Since code comes from geocaching.com, there's not an easy way of avoiding it. On some browsers the "yes" alert may come with a tick box that you can use to stop further alerts, but this will only work until you re-load the page or Groundspeak fix the code properly (which should be trivial!).

 

For the nerdy, the main maps page downloads a utility script (with a really long address starting http://www.geocaching.com/ScriptResource.axd?d= followed by a string of random characters). This includes a DateTime module containing the offending function:

 

DateTime.isLeapYear = function (year) {
   if (((year % 4 == 0) && (year % 100 != 0)) || (year % 400 == 0)) {
       alert("yes");
       return true;
   }
   return false;
};

Basically, every time this function runs during a leap year, it pops up "Yes" - it looks like a leftover bit of debugging code. From what I can guess, this will happen every ten minutes, but only for Premium Members (which may be why I've not seen the problem).

 

That's my guess at the explanation, hopefully there will be a fix along soon...

 

JRI

 

I like you explanation the best but if it is going to last all year for premium members maybe I should not renew on Jan 3 as I am suppose to and all other premium members should not renew the subscription and that might get the programmers working a little faster on fixing this problem.

 

That's the definitive answer as to what is producing the pop window (that's what the alert() function does) and the fix is simple; a GS programmer just needs to remove the alert("yes") line. It would be worth looking at the source code for the maps page to see what is calling the Datetime.isLeapYear function but it sounds like it's in a few places.

jholly

jholly

Posted
Posted

Someone up there needs to pull Jeremy out from under his desk, take the lampshade off his head and throw a bucket of cold water on him.

Didn't they do something like that to him last August?

team tisri

team tisri

Posted
  • Author
Posted

This issue has been pinpointed and fixed.

Thanks for the report!

 

Cool, let me leave my maps open overnight and see if I have an error when I return in the morning.

 

It no longer says "yes" all the time. THanks.

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...
×
Followers 1
Go to topic listing
×
×
  • Create New...