Last modified: 2014-02-12 19:55:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49355, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47355 - KML queries get wrong offset
KML queries get wrong offset
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticMaps (Other open bugs)
REL1_19-branch
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-18 08:59 UTC by Mathias Lidal
Modified: 2014-02-12 19:55 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mathias Lidal 2013-04-18 08:59:58 UTC
Hello. I just noticed that all KML query get the wrong value for offset. The problem is the use of getQueryLink(), which according to the documentation creates a link to further query results. This means that you will get a link to a query for the next results after the ones you're actually searching for 

For instance, if you set a very high limit (to get all results) you will actually get no results, as the offset is set to one more than the actual number of results.
Comment 1 Gerrit Notification Bot 2013-08-11 17:22:11 UTC
Change 71324 had a related patch set uploaded by Nemo bis:
Set correct default-value for offset

https://gerrit.wikimedia.org/r/71324
Comment 2 Gerrit Notification Bot 2013-09-25 19:14:11 UTC
Change 71324 merged by jenkins-bot:
Set correct default-value for offset

https://gerrit.wikimedia.org/r/71324
Comment 3 Andre Klapper 2014-02-12 15:57:28 UTC
Patch was merged month ago - is there more work left here, or can you close this ticket as RESOLVED FIXED?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links