TheAprilFools

I don't see how a greaseMonkey Script will change whats included in a PQ, I just think the date ranges for PQ's and the allowable placement dates on queries should be consistent, maybe a developer can comment.

Thats an acceptable solution for me, all I ask is that there be a way to setup a PQ where the date range includes all allowable values of placement date.

This has happened to me quite a bit today.

I have a number of PQ's that I use to map out my local area, these all centered on my home coordinates and use placement date to to segragate which caches are generated into each of the queries. This has been discussed many times and works well, but I have recently noticed one small problem. I discovered that a couple local caches have placement dates that are well before the minimum 1993 date that a PQ allows, once cache has a placement date if 1908 and the other has 1963. Im sure the cache owners have valid reasons for doing this, and the system allows the cache owners to enter the dates, but its impossible to setup a PQ using date range that will include them. I would suggest, that either when ever you setup a PQ where the start of the date range is 1/1/1993 that all caches before that date are also included or allow the start or end of a PQ date range to be blank in which case all cases before the end date (if the start date is blank) or all cases after the start date (if the end date is blank) would be included.

Cool, thanks.

I went into one of my bookmark lists and then went to edit one of the entries, it was my list of FTF and I wanted to put my find date in the comments, it did not have a comment before. I entered: April 17, 2005 And pushed "Update Bookmark" and this is the output I got: Server Error in '/' Application. -------------------------------------------------------------------------------- Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

I show everything that you have checked to run today (4 different PQs) as having run 2-3 hours ago. Thanks for the quick reply, sorry I had a brain fade and was thinking it was wednesday .

I submitted a new PQ about 4 hours ago and it has not run yet.

Four of my five regular queries ran after a long delay, the last one I cancelled, created a copy of it and set it to run in its place, but it still has not fired off.

I have been looking at the iPhone app also and have been thinking about getting it but the inability to log seams like a fatal flaw to me. Also the inability to be able to enter your own coordinates to track is a serious limitation if your trying to find either a multi or a puzzle cache. As it is it seams only suited to going for that FTF when you have left your GPS at home. Are TPTB purposly limiting the iPhone app to not disturb there friends at Garmin and Magellan?

Its almost irrelevant but its pretty clear its a bug, I got this text in a notification email today. Note that there is no direction indicator after the distance. In this case its due south of my home coordinates (179.98 degrees).

When I have used this feature, I have only used the LE setting. Usually to screen out caches in terrain I won't have the time or energy to find.

That does seam strange, I would think the system should prevent you from posting logs with future dates.

Using the same mechanism to define PQ's and notifications would make them more much more powerful and useful. I for one have been pushing for a change in notifications where I can filter out notifications for caches I have already found.

Does the GC.com database even support multi-byte character sets? Without that chinese characters would be impossible, even if the user has the right character sets installed.

While I really like this new feature, there is one small thing I noticed. Before when you click the button to 'Add to Queue', the button would disable itself with an indication that the job had been added to the queue and eventually whould show the job had been run. Now after the button is pushed there is no indication that anything had happened. Eventually, it will show the job has been run.

I never liked Waymarking, two main reasons: I disliked locationless caches and therefore was not inclined to there replacement, and second its separate. Not so much the smileys but just that its a separate site and the data has to be processed differently. I like the approach to earthcaches, consistent standards and a reviewing body for them.

I suspect that cheating is going on but its not due to the notification. Its probable that the owner gave them advanced info on the cache. I believe the normal edicate is that if someone is with the owner when they place the cache or otherwise gets advanced info, they can log the cache but not until the FTF'er does and there note in the cache log should indicate that its not the FTF.

You don't need to log a needs maintenance, as the owner you can edit the attributes and toggle the needs maintenance attribute.

Duplicate

You can setup a PQ for all caches you own that have the 'needs maintenance' attribute set.

While it feels wrong I don't have too much problem allowing owners to log a cache, although I won't myself. There have been times when a cache owner going to check on there cache has to do as much searching to find it as any other cacher since those other cachers have all moved the cache a few inches each so eventually its nowhere near where it originally started. I would much rather TPTB prevent multiple find logs by the same cacher on the same cache.

I had this happen to me once, it turned out I had too many PQ's. Try deleting one of your existing PQ's and try again.

I don't know about anybody else, but I have no expectation of privacy when posting any log type on a cache, since I know the text I enter will be visible on a public website.

I think its a good idea. Maybe if TPTB implement this they could also add a setting the user could set where they can set there 'blog' to show all logs, only find logs or none.