Last modified: 2010-08-06 12:18:01 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 T26665, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24665 - edit api conflict on deleted and restored files.
edit api conflict on deleted and restored files.
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.17.x
All All
: Normal normal (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-04 23:46 UTC by Derk-Jan Hartman
Modified: 2010-08-06 12:18 UTC (History)
5 users (show)

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


Attachments

Description Derk-Jan Hartman 2010-08-04 23:46:00 UTC
I experienced an issue trying to use edit api on this file: http://commons.wikimedia.org/w/index.php?title=File:Concert.jpg 

This happened after I had deleted and then restored the page, see also the log of that here: http://commons.wikimedia.org/w/index.php?title=File:Concert.jpg&action=delete . Whatever I tried, I couldn't make an edit to that page then. Every time I got: {"error":{"code":"pagedeleted","info":"The page has been deleted since you fetched its timestamp"}}

I tried purging the page and my browser, tried waiting a while (2 hours) and switching browsers, the problem would not go away. Perhaps the delete and restore timestamps were too close, confusing editconflict detection, or possibly, the api is looking at the last time of deletion and last time of edit, not realising that an undeletion of the page is an event that can occur after those two times.

I finally solved it by making an edit to the page with the normal interface. After that, everything went like clock work.
Comment 1 Roan Kattouw 2010-08-06 12:18:01 UTC
Fixed in r70557. The bug was in the code faking the value of starttimestamp when it's not specified. It would have been possible to resolve this situation without editing through the UI by simply setting starttimestamp to a timestamp after the deletion.

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


Navigation
Links