Ticket Information - ID: #269
| ID: | Category: | Severity | Reproducibility | Date Submitted | Updated By: |
|---|---|---|---|---|---|
| 0000269 | Bug Reporting | normal | always | 10/10/09 01:56AM | demeli |
|
|
| Summary: | API requests for tags returns results in random order (and more) |
| Description: | When you perform an API request with the "tags" GET variable set, results are not returned oldest->newest, but in random order. When you perform an API request WITHOUT the "tags" GET variable set, results are returned correctly. Compare: <http://gelbooru.com/index.php?page=dapi&s=post&q=index&tags=translated&pid=100> <posts count="11766" offset="0"> <post [...] id="595579" [...] /> <post [...] id="1789" [...] /> <post [...] id="9112" [...] /> [...] </posts> <http://gelbooru.com/index.php?page=dapi&s=post&q=index&pid=100> <posts count="11766" offset="0"> <post [...] id="1" [...] /> <post [...] id="2" [...] /> <post [...] id="3" [...] /> [...] </posts> ------------------------ Another bug: When performing an API request with tags (e.g. the one above), "change" is always: change="1247703968" instead of the UNIX timestamp of the post. ------------------------ And another minor issue: <http://gelbooru.com/index.php?page=dapi&s=post&q=index&tags=asdsadasasdads&pid=0> This tag "asdsadasasdads" does not have any posts. <response success="false" reason="Search error: No results found."/> Is a bad result to return IMHO. The search did succeed after all; it just didn't find anything. A better result would be <posts count="0" offset="0" /> |
| Additional Info: |
demeli replied at 2009-10-12 10:53:42  |
| All of these issues seem to have been fixed. Thanks Geltas! There are some remaining issues for full Danbooru compatibility listed here if you want to go the extra mile and make it perfect. :-) http://zabadab.eu/gelbooru.txt |