Page MenuHomePhabricator

Special:Export - create error message if #revisions exceeds limit for export
Closed, ResolvedPublic

Description

Author: elwp

Description:
Every attempt to export a long page history (>>100 revisions, eg. de:Bier, 1400
revisions)
fails with either

Sorry- we have a problem...
The wikimedia web server didn't return any response to your request.

or, sometimes,

<html><body></body></html>

How about options like "limit" and "offset"? The following URL could then be
used to export the first 100 revisions.

http://de.wikipedia.org/wiki/Spezial:Export?action=submit&pages=Bier&limit=100&offset=0


Version: unspecified
Severity: normal

Details

Reference
bz1748
Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Add Instrument class to PHP libraryrepos/data-engineering/metrics-platform!85cjmingT374840-add-experiment-enrollment-php-librarymain
integrate with Catalyst APIrepos/abstract-wiki/aw-ci-chart!30jnucheT374864main
support Catalyst chart defaultsrepos/test-platform/catalyst/catalyst-api!65jnucheT374864main
codfw1dev: track novaproxy.codfw1dev.wmcloud.org recordrepos/cloud/cloud-vps/tofu-infra!57aborreroarturo-113-codfw1dev-track-novmain
eqiad1: network: secgroups: expand coverage in cloudinfra and project-proxyrepos/cloud/cloud-vps/tofu-infra!47aborreroarturo-463-eqiad1-network-secgmain
tofu-infra: add support for neutron security groupsrepos/cloud/cloud-vps/tofu-infra!46aborreroarturo-323-tofu-infra-add-suppmain
Customize query in GitLab

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 8:17 PM
bzimport set Reference to bz1748.
bzimport added a subscriber: Unknown Object (MLST).

Update after implementation of r15101:

  • No error "Sorry- we have a problem..." anymore
  • If number of revisions exceeds the limit of 100, Special:Export delivers the

<siteinfo>...</siteinfo> section only.

Possible solutions:

  1. See initial comment of El (limit and offset)
  2. Create error message "Too many revisions, no export incl. revisions

possible." or something else

If 1. is too complicate/expensive I prefer 2 as a faster solution. Summary updated.

elwp wrote:

MediaWiki API now provides the desired functionality.