Jump to content

Kalkendotters

+Premium Members
  • Posts

    318
  • Joined

  • Last visited

Everything posted by Kalkendotters

  1. Is this a worldwide action, or only for the USA ?
  2. Direct-links to website do not function (sometimes) thread: http://forums.Groundspeak.com/GC/index.php?showtopic=175420
  3. This is the same error as discussed in this thread They just switched on/off some extra error-reporting
  4. see this trhread: http://forums.Groundspeak.com/GC/index.php?showtopic=175420
  5. It looks like it is just something that the cache-owner did on making his/her cachepage... Just add the neccesary HTML code around the placed-name, and you got some nice outstanding name. One of the places where HTML is not yet filtered out. (just like you could do to add an image to your travel-bug)
  6. See this thread: http://forums.Groundspeak.com/GC/index.php?showtopic=175420
  7. And the final part of the puzzle: This only happens when the cache has additional waypoints. If no additional waypoints have to be shown for this cache the direct link wil not give an error. If there are add-wps the site has to have a correct asp_session_id or you will receive the server-error.
  8. I don't pretend to understand that, but it certainly works as you describe. But what does it prove? And, more importantly, how do I fix it permanently? Or is this something for Groundspeak? It certainly didn't happen before last week's changes. This gives you a workaround till Grounspeak corrects it: first open www.geocaching.com in a separate IE-window, and only then click on the cache-links.
  9. I think it has something to do with the ASP_session cookies: If you have not visisted gc.com in this session, a direct link to a cache_details page (sometimes) fails. If you visit gc.com main page, and try the link again it suddenly works. (In the meantime the server has sent an ASP_SESSION_id cookie to your browser) try this: (first close all browser windows, or make sure you have not visited gc.com in this session) visit link http://www.geocaching.com/seek/cache_detai...3b-59a03e3c29f0 if this gives an error, goto: http://www.geocaching.com/seek and after that retry the link above; it suddenly works like it should.
  10. Seems to be working correctly again. Thanks; just in time for the weekend
  11. At the bottom of the list of caches (e.g. new cache in the Netherlands) there is an extra line with the page-back/forward controls. like: Total Records: 0 - Page: 1 of 0 Prev. << <[]> >> Next this extra one is just below the 'doenload waypoints' button
  12. Currently the new version is active on the site, but sadly the new version still delivers almost empty PDF-files. Could you please look into it, before the definitive switch-over to the new code-version ?
  13. The site reverted back to the old version, so now it is working again.
  14. When I try to view the PDF file of the cache, the resulting PDF is almost empty... It had only the coordinates, the waypointname (GCxx), the coordinates and the hints. All the other info is missing, like: short and long description, attributes and logs This is probably a side effect of the update, because it also happend 2 weeks ago when the site was temporary updated to .NET 2.0.
  15. Can't see the log: View a Cache Log You cannot see logs for unpublished listings. You can probably only see your own logs on unpublished caches...
  16. The country referred to is probably "Burkina Faso". Most of the refrences on google that show Burxina don't have Burkina Faso in the list. And some even use is as Burxina Faso. The UN-list of countries also does not have a reference to Burxina So it probably should be deleted from the countrylist
  17. The one you are missing will be a revoked (de-published) cache. See also this link
  18. If I read the description correctly, you just have to go to the mentioned waypoint. There you will find the information you need to open the safe... since the description says: "Deze cache willen we niet aan de grote klok hangen maar ........ noteer wel wanneer Maarten weer van zich heeft laten horen." Also: dont get help for mysterycache on a forum. Everything you 'say' here will be available through some googling, so others can easely solve the mystery
  19. Bump (still not working as it should)
  20. If you look under Geocache Information for User: hurbie you will see a total of 959 caches found. When you click on the link All Cache Finds only 956 are shown (really, I've counted them all ) So where are the 3 missing ones ? 1 is the Locationless cache that he found; which is known to not show up in the list. The other 2 are revoked/unpublished caches that he had found (specifically GCM8QB GCHHZC) Moral of the story: dont trust the total records that is shown on the 'All cache finds' page.
  21. Just reuse them for your next cache. Because they have an older GCnumber they will appear on top of the reviewer list.
  22. I think there should be a distiction for the waypoints in a multi with regard to the 'saturation/confusion' problem. Waypoints where information for the cache is hidden (micro, coordinate tag,..) should be counted for the proximity to other caches/states. Waypoints where normaly available information is used (plaquette, numbers on lightmasts, routenumbers,...) should not be included. It also seems that some reviewers miss the fact that it is a guideline, and not a hard to follow rule. quote: The reviewers use a rule of thumb that caches placed within .10 miles (528 feet or 161 meters) of another cache may not be listed on the site. This is an arbitrary distance and is just a guideline, but the ultimate goal is to reduce the number of caches hidden in a particular area and to reduce confusion that might otherwise result when one cache is found while looking for another. This guideline applies to all stages of multicaches and mystery/puzzle caches, except for any 'bogus' posted coordinates for a puzzle cache. endquot
×
×
  • Create New...