Last modified: 2014-01-22 17:46: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 T62330, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60330 - API:Purge - forcerecursivelinkupdate not reflected in API response
API:Purge - forcerecursivelinkupdate not reflected in API response
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.23.0
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-22 09:07 UTC by Lokal_Profil
Modified: 2014-01-22 17:46 UTC (History)
4 users (show)

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


Attachments

Description Lokal_Profil 2014-01-22 09:07:06 UTC
The forcerecursivelinkupdate parameter is not reflected in the API response for the Purge module. 

It is also (to me) unclear whether it actually triggers a cascading link table update since the job queue remains largely unchanged (even for high use templates).

To reproduce:
0) Log-in
1) go to https://commons.wikimedia.org/w/api.php?action=purge&format=json&forcelinkupdate=&forcerecursivelinkupdate=&titles=Template%3AWLPA-se (Low use template)

Returned: {"purge":[{"ns":10,"title":"Template:WLPA-se","purged":"","linkupdate":""}]}
Expected: {"purge":[{"ns":10,"title":"Template:WLPA-se","purged":"","linkupdate":"","recursivelinkupdate":""}]}
Comment 1 Brad Jorsch 2014-01-22 17:46:57 UTC
If "linkupdate" appears in the result then the forcerecursivelinkupdate will have been passed to the links update job, and the API has no way of knowing anything beyond that. I don't see the point of adding yet another flag to the result.

Due to the way links update jobs work, there will not be a large effect on the job queue.

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


Navigation
Links