Jump to content

LeGodFather

+Premium Members
  • Posts

    514
  • Joined

  • Last visited

Everything posted by LeGodFather

  1. It might be blocking only certain source ips as I am able to log from a different service provider! EDIT: Ok, strike that.. Just like Ace862 (below) I can from any service provider.. but, it's not working from FireFox, but it does from IE!
  2. Same here, for the past 10 mins this is what I get on any GC.com pages:
  3. Hmm.. you mentionned special characters, so I guess that would be the problem reported here..
  4. Is there a plan to fix this anytime soon? Not only it is in GPX files as mentionned above, but I see in the "All Geocache State Search" as shown below:
  5. Hi, I've downloaded 2 .GPX files from 2 different cache pages. In the the "Placed by" field I get this: <Groundspeak:placed_by>Tichris et C& #233;c& #233;02</Groundspeak:placed_by> instead of <Groundspeak:placed_by>Tichris et Cécé02</Groundspeak:placed_by> Here are the examples of the newer cache and one of the older cache. I see that the newer cache has the "& #233" in the file and the other the "é".. Could this have anything to do with this announcement - about the HTML being removed from the placed by field? Thanks for reading.. Edit: I have to insert a space between the & and the # so it would show in the forum.. but, there are no spaces in the GPX files. Finally, it also applies to .GPX files received from PQs.
  6. J'allais donner la même référence! Mais, Lewis82 est plus rapide que moi ce matin!
  7. Here, print this whole page and he will get a good idea of what it is. http://www.cdg.qc.ca/pages/geocachette.htm
  8. Bravo!! pour ton bénévolat, ta B.A., ton implication!
  9. Well, I'm getting the same errors both at home and on my computer at work. Edit to add: home computer: Windows XP; IE6 Same here.. FireBug says it's that line that is in error.. <script src="http://www.google-analytics.com/adurchin.js" type="text/javascript"></script><script type="text/javascript">_uacct = "UA-2020240-1";urchinTracker();</script>
  10. Reported problems & status: Google Maps: a bad char in cache name break the code. STATUS: We're looking at this now (this thread) Google Maps: if you zoom out so 500 caches are shown, no more update are done after that. STATUS: Thanks for letting us know, we're still working out the kinks (this thread) Send to GPSr: blue flag icon instead of chest icon are sent. STATUS: Works intermittently. Garmin changed the way they the JS was written. I've already contacted them about it and they will be changing what they need to (this thread) Pocket Query: PQ preview in Google maps not available STATUS: Just a quick note to let you guys know we're still very close to completing these maps. It would have been done by now but we found new ways to make it even better so we needed a bit more time for implementation. Thanks for all your patience. (this thread) *Server Error in '/' Application. Runtime Error *STATUS: There are many threads about this one.. here are a few: this thread, this thread, this thread, and this one, this one, this one and I could keep going on. They do not seem to be specific to any one page. I usually get the page I want with a few (2-3) page refresh.. I haven't read all the threads, so I don't know what is GoundSpeak's take on this.. The most recent thread talking about this error has had no intervention from GS. *Pocket Query: PQ date selection restricted to 2007 *STATUS: Fixed as of October 26th. (this thread) Print to PDF: when looking at the cache, the Print PDF button and (5 logs, 10 logs) does nothing. STATUS: fixed as of October 12th. Google Maps: 15 miles limit issue/disliking. STATUS: fixed as of October 15th. Pocket Query: First date non-inclusise. STATUS: fixed as of October 19th. P.S. This list is for now user updated to our best knowledge. Please help updating it if you know about an issue. Also please keep it simple, no personal feature request, try to focus on real bugs only. If you are not good at editing/updating a post so the look remain similar, please simply write in text and someone else will update later. Latest updates will always be shown on the last message so move down! Added by GF: To keep this thread as lean and clean as possible we should open a different thread/subject to discuss the issues.. and report here the thread you opened with the link to the thread. Thanks. Edit: added the "/" application runtime error
  11. Oui.. mais, là, ça parle de la nouvelle réalité des reviewers en France et en Wallonie.. tandis qu'ici, nous saluons un ami géocacheur.
  12. Alain/Habot.. merci pour les remplacements à l'époque où il y avait moins de "réviseur" (Reviewer à la Québécoise) Canadien.. et aussi pour avoir partagé ton expérience avec nous et avoir répondu à nos multiples questions, sur notre forum Québécois (http://www.geocaching-qc.com/phpBB2). Merci!
  13. Wouldn't that be a feature request?
  14. Reported problems & status: Google Maps: a bad char in cache name break the code. STATUS: we are still looking at this issue Print to PDF: when looking at the cache, the Print PDF button and (5 logs, 10 logs) does nothing. STATUS: fixed as of October 12th. Google Maps: if you zoom out so 500 caches are shown, no more update are done after that. STATUS: we are aware of this but we focus on higher priority 1st Google Maps: 15 miles limit issue/disliking. STATUS: fixed as of October 15th. Send to GPSr: blue flag icon instead of chest icon are sent. STATUS: we are still looking at this issue, we may have a fix before the next weekend Pocket Query: First date non-inclusise. STATUS: fixed as of October 19th. Pocket Query: PQ date selection restricted to 2007 STATUS: we are aware of this Added 2 more.. Good job Rhialto!
  15. It was not addressed to me.. but, from my point of view, it does look like it sometimes. For example, when you see something new for a brief period and than it's not there.. that's looks like they are testing stuff live.. I'm not saying they are not testing before.. maybe just not enough? Maybe they shouldn't have the same standards as giants like Goggle or financial institutions because it's a hobby/leisure/sport service.. but, we are still customers.. as we do have expectations.. So.. my thoughts on the "known bugs list".. I would like to be able to go to a specific post (tracking it would make it so easy) and know what's going on and not have to browse all over the forum for specific issues.
  16. Although the other issue seems to be resolved.. this one is still pending.
  17. It's Friday, and I got all my PQs for the week. And, it looks like it was only the "Preview Pocket Query" that was not returning the caches placed on the first day of the PQs dates. And.. I've just ran (3 times) a "Preview Pocket Query" and it looks (once again) like it has been fixed. It does show the caches of the first date. Anyone can confirm this? I'm happy with what I have now. Thank you!
  18. This was 4 days ago. Meanwhile we are getting incomplete data. My thoughts exactly. Maybe I expect too much because I work in an IT world where we have to give updates every 2 hours when there is a problem. We're just asking for an update.. every 2 hours is probably too much in this case.. maybe every 2 days? Anyways..
  19. Yes.. this is the other thread.. I agree that it's a seperate issue.. but, they are all part of a Pocket Query issues!
  20. You are right Alan.. I just ran a PQ preview, the same a I ran this morning and I'm too missing caches. But, at the time of my post, I'm sure it was working!
×
×
  • Create New...