+lodgebarn Posted January 27, 2020 Share Posted January 27, 2020 I am running the same type of api call as have done for the past few months. For instance Other, State West Midlands. Sort descending, Get 250 caches. I can see the API call has the correct sort order at the end &Sort=id- but I am always being returned the earliest caches not the most recent. This was working fine yesterday. A resolution would be most welcome. Thanks 1 Quote Link to comment
Moun10Bike Posted January 27, 2020 Share Posted January 27, 2020 Thanks for reporting this. The engineers say it should now be fixed. 2 Quote Link to comment
+lodgebarn Posted January 27, 2020 Author Share Posted January 27, 2020 18 minutes ago, Moun10Bike said: Thanks for reporting this. The engineers say it should now be fixed. Brilliant all good now, many thanks for the quick fix. Quote Link to comment
+HHL Posted January 27, 2020 Share Posted January 27, 2020 (edited) 54 minutes ago, Moun10Bike said: Thanks for reporting this. The engineers say it should now be fixed. It's fixed for cache ids now. But the bug still appears with sort by name-. Hans Edited January 27, 2020 by HHL Quote Link to comment
Moun10Bike Posted January 27, 2020 Share Posted January 27, 2020 1 hour ago, HHL said: It's fixed for cache ids now. But the bug still appears with sort by name-. Hans Thanks - all should be working correctly now. 1 Quote Link to comment
+HHL Posted January 27, 2020 Share Posted January 27, 2020 Thanks again. Happy Coding Hans 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.