+Zabhood Posted August 14, 2014 Share Posted August 14, 2014 Hi. I think that I've found a bug of some sort. When I'm running a PQ with the "include attribute" set and the "seasonal access" set to NO the result of the PQ returns all sorts of caches. Both caches with and without the right attribute and caches with the attribute set both to YES and NO. In other words I can't use the PQ request for anything useful for that particular attribute. Other attribute PQ's seam to work but not for this attribute. Please fix. Best regards Quote Link to comment
Moun10Bike Posted August 14, 2014 Share Posted August 14, 2014 I just tried this and the PQ is operating as expected. Do you have an example PQ that is showing this behavior (I looked in your list and didn't see one offhand). Quote Link to comment
+Zabhood Posted August 14, 2014 Author Share Posted August 14, 2014 (edited) Do you have an example PQ that is showing this behavior (I looked in your list and didn't see one offhand). I've made a PQ called "NO seasonal attribute set - in Denmark" which resulted in 17 caches. Four of them doesn't have the current requested attribute. http://coord.info/GC4A7HF http://coord.info/GC4RB2D http://coord.info/GC3PXR1 and http://coord.info/GC3PFY6 A list of the result of the current PQ can be seen here. http://www.geocaching.com/bookmarks/view.aspx?guid=36a40b6e-772e-433d-9195-22537beb3426 Best regards Edited August 14, 2014 by Zabhood Quote Link to comment
Moun10Bike Posted August 14, 2014 Share Posted August 14, 2014 It does appear that the logic is not correctly recognizing the value of the excluded attribute. I will enter a bug. Thanks! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.