OK, Groundspeak like to 'improve' things but they could at least be consistent!

[+Delta68]

The Event Calender page is not fit for purpose. This is fact! not just my opinion. Some time ago I wrote a GreaseMonkey script which stored distances etc in the 'nearest.aspx' page using the GUID as a key and then displayed them next to the event details on the Calender page. It also filtered out all countries I had no interest in.

 

Sounds messy but it worked fine for a few years until the last site update; now guid is no longer used in the nearest.aspx page (it uses a combination of gc code and name instead) but guid IS still used in the calender page rendering my GM script useless

 

So, like I say,

'Improve' things by all means but at least be consistent!

 

:mad:

 

I am under no illusion that this will make one jot of difference.

[+niraD]

GreaseMonkey scripts are essentially treating the markup, CSS, JavaScript, etc. of the geocaching.com site as a public API. They are not a public API.

 

I think it is completely unreasonable to expect Groundspeak to improve (i.e., change) things without affecting any of the GreaseMonkey scripts that rely on their markup, CSS, JavaScript, etc. in unknown and unpredictable ways.

[+Delta68]

Well I've fixed this particular script now.

It just seemed strange to me how they stopped using the guid in links on one page but continue to use it in a functionally very similar page

 

 

Mark