Jump to content

techiegrl64

+Premium Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by techiegrl64

  1. To clarify, I have been attempting to remove only one item at a time. It was working last evening (although quite slowly) but this morning it is not (500-Server Error).
  2. Tried it again last evening and actually managed to delete a few items from my watchlist via GSAK and directly from the watchlist page. Unfortunately, this morning it is not working again...back to the same "500 - Server Error".
  3. Apologies, I should have included the error specifics.....it is "500 - Server Error". You're welcome to test removals with any of the following caches on my watchlist: #1-1970-I Think I Love You #2-1970-War #3-1970-The Tears of a Clown #4-1970-Mama Told Me (Not To Come) #5-1970-I Want You Back #6-1970-Venus #8-1970-Vehicle #9-1970-Spirit In The Sky
  4. No, it is happening on a regular basis with many caches. I notice that when the gc.com page comes up and asks me to confirm it takes a verrrry long time to load. BTW, which entry did you delete from my watchlist? Thanks, Joan (Techiegrl64)
  5. I get a HTTP error whenever I try to delete items from my watchlist. I can add items just fine, but deleting them results in an error no matter if I try deleting via GSAK, the watch list directly, or by selecting 'Remove from Watchlist' on the cache page. The same occurs if I delete my browser history, and I have tried this in Chrome as well as MSIE. This has been going on for months and my watchlist has far too many entries now. Is there a fix or workaround? Thanks!
  6. If this point has already been raised please forgive me -- I did not find it in the threads. Following a recent change to the Web site I noticed that the display behavior for cache logs shown at the bottom of the page is unusual. Very often it will display a set of logs somewhere at the beginning or middle of the log chronology. In those instances you have to perform extra keystrokes to see the most recent (first page) logs. When I am looking at caches I am more interested in the recent activity, not something that took place years before. Using Windows Vista and Chrome 19.0.1084.46.
  7. Are there any plans to distribute a souvenir on the site for cachers who found caches on 11-11-11? Thanks, Techiegrl64
  8. I have absolutely no background in geology whatsoever, not even any courses in college on the subject. I enjoy doing Earthcaches and most of them have been very interesting and informative, and I have had the pleasure of seeing some memorable and scenic vistas as a result. On occasion I have struggled to understand them when they are written in extremely technical terms. I usually try to find Earthcaches in the places where I travel but every once in awhile I pass one up if it so complicated as to require an advanced scientific degree to understand and/or complete.
  9. I don't know if this is reported already but I wanted to make sure it is identified. I received a log deletion notice on a geocoin that I found/moved and noticed the following: 1) the smartlink references a "GC" number when in fact the prefix on the traveler should be "TB". Here is an excerpt from the email (the id should be TBTNYY): Visit this listing at the below address: http://coord.info/GCTNYY 2) the email has no link of any kind to the actual log entry, the date of the activity (only shows the date this log was deleted), the text of the entry, or any other useful information to track it down. Perhaps it is different for geocoins (I would think not) but when a geocache log is deleted there used to be a link to the actual text of my entry so I could go back and see what I had written to see the date of the entry, the text, and try to figure out if I had fat-fingered the geocache id. The way it stands now I have no way of seeing my log entry or even seeing the date the activity occurred.
  10. I was on a week-long road trip and set up several PQs for various areas and routes where I would be traveling. I generated the PQs and had the output ready for download. I had reached the max of 40 and needed a couple of ad hoc PQs to make a special caching run in that area so I deleted one that I'd already generated. I was surprised to discover it also deleted the file that was ready for download! It is fine to delete the source PQ that generates a result set but it does not seem correct that the result set which was already prepared would be deleted as well.
  11. I am using Windows XP Professional with MSIE 7.0.5730 (and I just upgraded to MSIE 7 because of the previous site changes that made it impossible for me to search on the previous version). From the "Seek A Cache" page (http://www.geocaching.com/seek/default.aspx) I am getting errors on nearly every single type of search. I have taken screen captures of all the errors, and they all have the same error message followed by the parameters applicable for that type of search: "Internet Explorer cannot open the Internet site http://www.geocaching.com/seek/nearest.asp.....<parameter values here>....Operation aborted." These searches are giving me the error indicated above: by address, by friend name, by state, by zip code, by country, by keyword, by area code, hidden by username, found by username, by latitude/longitude in WGS84 datum. These errors are generated every single time I try any of these searches. Here is a specific example (by address search): "Internet Explorer cannot open the Internet site http://www.geocaching.com/seek/nearest.asp...64&dist=100. Operation aborted" So far the only searches that seem to work for me are: state page, Google maps, exact GC code. I am able to preview PQs at this time but that means I have to set up PQs and keep adjusting them around for trips that I am researching. I first noticed this error on Monday morning (I also encountered the 500 internal server errors while trying to upload photos yesterday).
  12. Ditto here -- brand new PQs set up on Wednesday and scheduled for Thursday have not run as of 0800hrs (Central time). Hoping it gets resolved soon so I can get ready for my weekend caching run.
  13. The GPX file was generated with GSAK. Files are copied from my laptop to the Oregon after powering it up in mass storage mode.
  14. If this has been discussed elsewhere please point me to the correct thread -- I wasn't able to locate such a discussion before posting this. I have a question about recognition of all waypoints when loading multiple GPX files on the Oregon (I have the Oregon 300). I created a GPX file containing my "permanent" waypoints -- coords to home, friends' houses, etc. I always load this file along with the fresh GPX file containing the caches for my day's run. I have noticed that sometimes the contents of the "permanent" waypoint file are not recognized after transferring both GPX files to the unit. There are approximately 20 waypoints in the "permanent" file and I usually load up about 1000 caches in the geocaching file. When transferring these GPX files I always place them into the GPX folder on the Oregon. I did upgrade last week to firmware version 2.98; however, I have noticed this problem several times since I bought the unit and it has occurred since the update. Thus, I don't believe the update caused the problem but it did not resolve it either (my purpose in updating was to get some of the new features such as waypoint averaging). Isn't the Oregon supposed to read all the GPX files that are loaded into the GPX folder? The only way that I have found to make sure that all my waypoints and caches are recognized is as follows: 1) reset all waypoints (to clean up the old junk) and power down 2) power up in mass storage mode and load up the permanent waypoint GPX, then power down 3) power up in GPS mode and let it read the waypoints (and verify that they're present), then power down 4) power up in mass storage mode and load up the GPX file containing caches, then power down 5) power up in GPS mode and double-check everything is there. Obviously this is a rather tedious process. Am I doing something wrong procedurally that is causing this problem? Is there a way to resolve the problem?
  15. I am having the same issues -- it has been somewhat frustrating. This has a significant impact on the speed of logging my caches, particularly when I'm logging for a long weekend when I have 100 or more cache logs to be entered. The page refresh seems to be centered around changing the format of the month from alphanumeric to numeric. This seems like a conversion that could be done in the background without a page refresh. On the front-end page I would prefer to see the alphanumeric form of the month to avoid logging errors caused by confusion with alternate date formats (mm/dd/yy versus dd/mm/yy).
  16. I have made another discovery about this anomaly. Apparently the cache in my own bookmark list will not show up if it is also in my Ignore list. Once removed from my Ignore list it shows up just fine. This is not behaving the same way it did before and defeats the purpose of my bookmark list. For example, I have "difficult/problematic" caches in a specific bookmark list and I also put them on my Ignore list so that I don't see them in my regular weekly cache runs after work (e.g., the easy ones that I can do in my work clothes). I run a PQ on this "difficult caches" bookmark list when I am going out to do the "hard" ones and the toughies that have difficult terrain or have bamfoozled me.
  17. I am experiencing a malfunction with the PQs based on bookmark lists. Furthermore, it seems to be limited to those based on my own bookmark lists. I have several PQs set up for bookmark lists, and I am able to preview the ones for bookmark lists owned by others; however, when I try to preview the PQ for the bookmark list that I own the preview comes up empty. I tried deleting the PQ and re-creating it but got the same result. I also confirmed that my bookmark list still exists and that it contains several caches (about 20 at this time). This problem occurs whether I try to preview with the "list" or the "map" type preview feature. I know this PQ was working yesterday morning (Thursday) around 9am Central time because I was using it. It stopped working sometime within the last 28 hours. Anybody else having this problem?
  18. I just dipped my geocoin twice in the past 20 minutes and neither time did the mileage update automatically. I still had to manually update the mileage. Bruce The updating may not be instantaneous. How long did you wait before checking the mileage? I tried updating mileage on a couple of my coins around midday today and the mileage has not been updated more than 6 hours later. I have quite a few coins that are patiently waiting for their mileage. Do we have to manually recalculate mileage on every single one or will the mileage gradually get updated as the missing mileage is backfilled after this fix?
  19. Yep. I'm getting this one too. I know that I copied several PQs yesterday, but during mid-afternoon I noticed the Geocaching.com site was unavailable with a front page indicating maintenance was under way. I noticed a problem with the PQ copy function early on Tuesday evening, after the site became available. I am still having the problem this morning (Wednesday) as of 0823hrs Central.
  20. My PQs ran okay on Saturday evening, but as of last evening they are not running at all. I made copies (again) and re-submitted on Sunday evening and received nothing. I repeated that again this morning and submitted for Monday and still nothing. My PQ page indicates they have not executed yet after more than 12 hours. Just a follow-up on my previous note -- my PQs started working sporadically around 9:30am Central on Monday morning. One of them ran as I had submitted it early on Monday morning, but the other two ran only after I made new copies of them (for the second time) and re-submitted them.
  21. My PQs ran okay on Saturday evening, but as of last evening they are not running at all. I made copies (again) and re-submitted on Sunday evening and received nothing. I repeated that again this morning and submitted for Monday and still nothing. My PQ page indicates they have not executed yet after more than 12 hours.
  22. I am having similar problems. I ran 2 PQs for my Sunday caching trip last evening at 6:15pm -- it is now 4:22am and I haven't received them. My Sunday plans have now switched to Plan B -- my caching buddy and I cannot go to the destination I had been planning for the last 2 weeks (now that I am off pager duty) but instead must go back to the area where I was caching on Saturday since that's the only data I have available at this time. My 2 PQs show they ran but I have not received the data in my Gmail account. I am receiving other email, including a few messages from GC.com for caches on my watch list. Apparently some of the other caching messages are coming through -- though perhaps not all since the number of messages seems sparse -- PQs are not coming at all.
  23. Add me to the growing list of folks who can't get their PQ results -- I don't schedule my queries to run regularly, so these are one-timers specifically based on the area I've decided to visit for the day. Downloading individual waypoints is going to be a real DRAG. So....if the queries set for Friday haven't run and it's already Saturday, does that mean I'm not going to get them and I now have to re-schedule for Saturday and get in back of the line again??? Sure would be nice to know if Groundspeak is working on the issue.
  24. We are planning a trip to Pennsylvania in 2 weeks. We plan to fly into Philadelphia on a Thursday and take a somewhat roundabout path over into New Jersey, down to Delaware, over to Maryland (figured we could pick up 4 new states on this trip!), and then up through Pennsylvania to stay with family in the Millville/Bloomsburg area for the weekend. To catch our return flight from Philadelphia we plan to drive back down through the eastern portion of Pennsylvania so we can pick up some additional counties. We're not familiar with that area and are looking for cache recommendations, including your favorites, historical, oldest caches, or just plain cool ones. Thanks for your help!
  25. Don't know if anybody has mentioned this yet but it seems that the caches along a route feature is broken. I am unable to save any new routes or even page through the routes I've already uploaded. At present I can only see page 1 of my existing saved routes. Apparently I can create PQs from the first page of routes that are visible, but unfortunately I was trying to set up a new route for an out-of-town trip I'm taking today. Guess I will not be caching on the way. Ditto on the comments of others to move the bug inventory back over to a sidebar instead of the bottom.
×
×
  • Create New...