Last modified: 2012-02-08 16:59:57 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 T35910, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33910 - CSV export incorrect offset
CSV export incorrect offset
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
PC Linux
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-23 19:08 UTC by edward.david.baker
Modified: 2012-02-08 16:59 UTC (History)
3 users (show)

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


Attachments

Description edward.david.baker 2012-01-23 19:08:28 UTC
When I create a query and set the format to CSV the resulting link always has an offset value set. Even when I try to force the offset to 0, the link to the CSV file will have 20 or 500 or some value seemingly dependent on the limit value. Switching the format from csv to table dumps all of the data properly.

Example 1:
{{#ask: [[Category:Test]]
| ?Col1
| format=csv
| limit=1000
| offset=0
}}
This results in a link with "offset=500&limit=1000&format=csv".

Example 2:
{{#ask: [[Category:Test]]
| ?Col1
| format=csv
| limit=100
| offset=0
}}
This results in a link with "offset=100&limit=100&format=csv".

Example 3:
{{#ask: [[Category:Test]]
| ?Col1
| format=csv
| limit=1000
| offset=2
}}
This results in a link with "offset=502&limit=1000&format=csv".

Versions:
Mediawiki 1.18.0
PHP 5.3.9
MySQL 5.0.26
Semantic Bundle 20120109
Semantic MediaWiki 1.7.0.1
Comment 1 Jeroen De Dauw 2012-01-23 19:18:52 UTC
Known issue introduced in 1.7.0.1, fixed in 1.7.0.2.
Comment 2 Tony Boyles 2012-02-08 16:59:57 UTC
(In reply to comment #1)
> Known issue introduced in 1.7.0.1, fixed in 1.7.0.2.

I'm also having this exact issue, and my SMW is at version 1.7.0.2.

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


Navigation
Links