Insta-notify Issue

[+the hermit crabs]

I posted this in the "Notification Service (beta)" thread, but it may have gotten lost in the general discussion of what a cool feature the insta-notify is. The same thing just happened again today -- we got a temporary-disable notification on a cache that has not yet been listed; it included issues that the reviewer has with the cache placement.

 

I really like the notification of newly-published caches, and the enable/disable notices on previously-published caches, but would there be a way to not send the enable/disable notifications for caches that have not yet been published? I feel like I'm reading someone else's mail when I get these

[Keystone]

The volunteer reviewers became aware of this over the weekend when working with new cache submissions. We brought it to Groundspeak's attention in our separate forum, and I do hope that this bug will be worked out. Unfortunately, with many dozens of reviewers scattered around the globe, not everyone read those messages, so some reviewers may still be using the "temporarily disable" option when dealing with new cache submissions. Thank you to everyone who brought this matter to light, and sorry for any confusion.

[Jeremy]

Thanks. I'll put some checks in there to avoid these notifications from going out.

[+denali7]

thanks, jeremy, this is a neat idea. i'm glad the notices are set up to apply to single cache types--i don't hunt them all, and like the idea that it will cut down on incoming e-mails by only putting the notify on traditionals.

[+the hermit crabs]

Thanks. I'll put some checks in there to avoid these notifications from going out.

not sure if that was supposed to have been fixed yet, but we're still getting the pre-approval enables and disable notifications. (if you're still working on it, sorry for bringing it up again)

[+the hermit crabs]

This issue seems like it may be worse now: I still get lots of notifications of enables and disables on unpublished caches, but in the last few days there have been some newly-published caches within my specified mileage range that I did not get a "published" notification for.

 

Is anyone else seeing this?

 

(edit: regarding the missing notifications, it's almost as if it doesn't recognize that I changed the mileage range after initially setting up the notifies. I think I initially had it at just 10 miles, then later I increased it. The one new-listing notify that I have received was within that 10-mile range; there have been at least two others that were within the larger range, after I made the range larger, that I did not get notifications for.)

Edited August 8, 2005 by the hermit crabs

[+beejay&esskay]

I just got an "archived" for a cache that had never been "published".

 

Log Date: 8/7/2005

Disabling cache due to no contact from owner with the last 30 days about modifying the cache.

 

I must say it was intriguing, but probably unnecessary to get this.

[+Joe Smith]

This is a great feature, and for now there are still some bugs. As with everything else, they will be fixed in time.

 

 

 

Joe Smith

[+the hermit crabs]

This is a great feature,  and for now there are still some bugs. As with everything else, they will be fixed in time.

 

 

 

  Joe Smith

Yep, I'm aware of that... but beta-testing is pointless if the testers don't report back what they're seeing, right?

 

That's all I was doing.

[+JMTBuzz]

This is not a bug report, but an enhancement suggestion. On electronic devices like pagers, text that can be received is limited in length. Can the coords for the cache be moved near the top of the notification, say following the distance and before the name of the logging Geocacher?