Jump to content

PeterNoG

+Premium Members
  • Posts

    281
  • Joined

  • Last visited

Posts posted by PeterNoG

  1. QUITE BUSTED! I can only get outdated Visited Stats, and can't even get outdated Posted stats at all - it goes straight to the outdated Visited ones! Put it this way, it 'says' that it is displaying "Posted", but they are actually "Visited".

     

    I have the opposite problem. I get Posted Stats (I don't know if they are up to date or not) when I want Posted Stats and also when I want Visited Stats.

     

    Interestingly, when I looked at Grahame Cookie's Stats, I got outdated Posted Stats (1013) for both Posted and Visited.

     

    It is REALLY BUSTED!!

  2. CDT I understand since that the zone I'm in too, but AZT and CET are confusing. Since most of jennyanykind's caches are from Arizona, I assume AZT is Arizona time but if you Google AZT most hits are for Azerbaijan Time. I think to most people, Arizona is either MST or MDT.

    CET is likely Central European Time but that could be Central European Standard Time (GMT+1) or

    Central European Summer Time (GMT+2)

     

    anyway

     

    At 13:00 CDT (GMT-6) I had no problem upload photos

    Again at 15:00, still no problem

  3. 11am-11:35 CDT

     

    Picture upload: 5/6 fails; 1 was uploaded

    An error occured in the File Upload Service. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

     

    Submit waymark: 4 failures

    3 of these: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    1 of these: This SqlTransaction has completed; it is no longer usable.

    4 email rec'd "We have received your new waymark submission:"

     

    Log Visit: 1 failure

    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

     

    Visit went thru on 2nd attempt, the picture fails on first attempt

    An error occured in the File Upload Service. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    Picture uploaded on 2nd attempt.

     

    Frustrating!

  4. I got a good variety of error messages over the last hour or so while trying to post two waymarks.

     

    Invalid operation. The connection is closed.

     

    This SqlTransaction has completed; it is no longer usable.

     

    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

     

    Object reference not set to an instance of an object.

     

    They finally went through.

  5. I don't know what is happening. Last night and this morning I have made several unsuccessful attempts to submit waymarks. A few are submitted but most are not.

     

    I get this message:

    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

     

    Over 5 minutes later I get an email with this message:

    "We have received your new waymark submission: <waymark name>"

     

    But it is still listed in my Unfinished Waymarks list and the waymark page says:

    "This waymark has not been sent for review yet."

     

    Picture uploading has also been difficult with frequent:

    An error occured in the File Upload Service. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

  6. I've been having a problem with Garmin Communicator on Firefox for several weeks. I don't know how many times I have reinstalled Garmin Communicator but Firefox still wants me to reinstall it. I've just been getting a GPX file, putting it into GSAK, filtering so it is just that cache then uploading that way. Lots of steps for a single cache.

    Today I finally checked out the forums and found this thread. Not much help but it got me thinking. I went to "Add-ons" in Firefox and saw that Garmin Communicator was set to "Never Activate". I never did that. Firefox must have done it during an 'upgrade'.

    I set Garmin Communicator to "Always Activate" and it works perfectly now.

  7. I have a saved bookmark that goes directly to my Pending Review list.

    http://www.Waymarking.com/wm/search.aspx?f=1&wo=True&wft=2&wst=8&uid=acd5fb48-4a8b-47e8-b2b5-5476cc4e9b44&st=16

     

    It doesn't include any waymarks that have been sent for a vote by the category leaders or has been declined. For those, I have another bookmark.

    http://www.Waymarking.com/wm/search.aspx?f=1&wo=True&wft=2&uid=acd5fb48-4a8b-47e8-b2b5-5476cc4e9b44&fw=True&st=40

  8. The Heartburn Series north of Palm Springs CA is spread out mostly on a square mile with the arrow extending a little father out.

    Salt Shaker - Heartburn Series by KNOCK

    The Heart itself are all traditional caches and the arrow is seven mystery caches that are solved with numbers from inside the traditionals. The seven final locations also create a mini pattern.

     

    7af96e7d-7803-43c8-9d67-9361fcfd12e8.jpg

  9. The "All Finds PQ" contains ALL your logs from any caches that you have found.

     

    A regular PQ contains the last 5 logs for each cache PLUS ALL your logs.

     

    Just bookmark all caches that you have logged BUT not found, then run a PQ on that bookmark list.

  10. We found coin #29 at Up Up and Away (GCHRQK) yesterday during the Rocky Mountain Balloon Festival. We surprised ourselves by finding the cache without our GPS. I had looked briefly at Google maps and since we were in the area, we gave it a try. Success.

    We didn't know anything about Mr Jiffy's contest before we found the coin so that was another nice surprise.

    We took this picture this morning and dropped the coin in Pint Size (GC1CHD6) a few hours later.

     

    eb1c7122-355a-4822-8712-3b4035e3f353.jpg

  11. I did a little testing and it looks like the line breaks are screwing up the plain test. If you enclosed each line that you want in plain text with the brackets it works fine. Check this example:

     

    [FTF. This turned out to be messy. Thinking back, this may be only the second time I've gone caching at night by myself. My glasses fogged up when I got out of the car and never really cleared. There was no light near the cache and I couldn't hold the flashlight and handle the cache and the logbook. Juggling all this took me 4-5 times as long as it would have in daylight. Next time I go at night I'll take my head lamp. There are few enough real caches, I sure hope this one survives. Took the FTF prize. No trade. Signed log. Thanks for the hunt.]

     

    [The encryptor doesn't work right so I had to put everything in the one paragraph above. This paragraph should not be encrypted but it is.]

     

    Ol gur jnl, gurer ner guerr gryrcubar cbyrf naq gjb be guerr gerrf. Znlor gur eryngvbafuvcf ner pyrnere va qnlyvtug.

  12. Personally, if someone is going to contact me about a cache, I would prefer it be through gc.com unless it is one of my close geofriends. And I don't think it is inappropriate if you email someone kindly and just say, "I am going to be visiting your area soon and was wondering the status of this cache. It looks like one I would really enjoy." That makes the cache owner feel good about his cache and not personally attacked. I think it is all in how you word it.

     

    I agree that a carefully worded email to the owner might be the better approach. An online log for a disabled cache that just questions when/if it will be active, seems more like "cache police" and can easily be taken the wrong way.

     

    "What do you know about this cache?" "When do you expect it to be placed back out to be found?"
    If you change the tone of your queries, I expect that you will get better responses.
×
×
  • Create New...